S4/hana mm & SD EDI Nast based integrated configuration (orders, ordrsp, desadv, invoice)

=>Reference

• Integrating MM & SD Modules in Same Client to Create Sales order in Supplying Company Code Using PO raised in Receiving Company Code By I-Doc Message Type ORDERS Part1
• Integrating MM & SD Modules in Same Client to Create Delivery in Supplying Company Code & do GR in Receiving Company Code By I-Doc Message Type DESADV Part2
• Integrating MM & SD Modules in Same Client to do Billing in Supplying Company Code & do LIV in Receiving Company Code By I-Doc Message Type INVOIC Part3
• How to set up ORDERS, ORDRSP, DESADV, INVOIC IDOCs interchange in the same system

1. Application scenarios

• Business scenario
  

2. The configuration process 1

• Configuration point overview
  
• buyer ：Create PO
  • 1.BP Create a supplier and maintain the corresponding customer code of the seller （ That is, the code of the buyer in the seller ）
    
  • 2.WE20 Create vendor partner parameter files and maintain outbound message types
    
    • Outbound message type ：ORDERS
      
    • Outbound message control
      
    • Outbound message overview
      
  • 3.MN04 Determine the output type
    
    
  • 4. Other configuration items to be confirmed
    • NACE-> The process （ The procedure contains condition types NEU）
      
    • NACS Condition type （ Condition type NEU Assign access order 001）
      
    • NACE-> Access order （ Access order 0001 contain Condition table 025;MN04/MN05/MN06 The maintenance condition table can be output and determined normally ）
      
    • NACE-> The output type （ Define the condition type NEU Output mode of ; Here we set it to EDI）
      
      
      
      
• Seller ：Create SO
  • 1.WE20 Create a logical system partner parameter file , And maintain the inbound message type
    
    • Inbound message type ：ORDERS
      
    • Inbound message overview
      
  • 2.VOE2 Maintenance table EDSDC
    
  • 3.VOE4 Maintenance table EDPAR
    
  • 3.VD01 Maintain customer information records （ establish SO Automatically bring out the customer material code ）
    

3. The configuration process 2

• Configuration point overview
  

• buyer ：Confirm PO

  • 1.WE20 Create purchasing logic system partners EQ1CLNT710 And set the inbound message class ORDRSP
    
    • Inbound message type ：ORDRSP
      
    • Inbound message overview
      
  • 2.ME12 Set the confirmation control code
    

• Seller ：Confirm SO

  • 1.WE20 Create a vendor customer partner 100000029 Partner type KU And set the outbound message type ORDRSP
    
    • Outbound message type ：ORDRSP
      
    • Message control
      
    • Outbound message overview
      
  • 2.VV11 Maintain sales order output records
    
    
    

4. The configuration process 3

• No demonstration for now

5. The configuration process 4

• No demonstration for now

6. test

• ED1CLNT300 Create purchase order , Order confirmation returned EQ1CLNT710 Automatically created SO
  
• ED1CLNT300 PO Output after creation EDI news
  
• EQ1CLNT710 Automatically generated SO
  
• ED1CLNT300 WE02->IDOC file
  
• EQ1CLNT710 WE02->IDOC file