MM-SD SCHEDULE AGREEMENT INTEGRATION

Mert_Atay · ‎2024 Mar 19

MM-SD SCHEDULE AGREEMENT INTEGRATION

A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement, or you can create them later.

You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have completed the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity.

In this blog, you can find EDI integration of purchasing and sales schedule agreements in the same or different system and the necessary adaptations to automate the process.

Organization Information

Receiver Company

Company Code: 1000
Purchase Organization: 1000
Supplier: 2000000000
Material Number: 10

Sales Company

Company Code: 1001
Sales Organization: ZPRO
Customer: 7000000001
Material Number: 9

1 Customizing

1.1 Define Unloading Point Partner Description is Plant

The system determines relevant sold-to party number based on data in the delivery schedule sent in by customer with Electronic Data Interchange.

SPRO à Sales and Distribution à Sales à Sales Document à Sales Scheduling Agreements with Delivery Schedules à Control EDI Inbound Processing à Execute Sold-to Party Assignment for Release Orders

1.1..png

1.2 Define Special Features for Delivery Schedules

You must define for each sold-to party or combination of sold-to party and unloading point how delivery schedules received through Electronic Data Interchange (EDI) are to be processed.

Note: You must create a record for each sold-to party. The system checks this record for every incoming delivery schedule.

SPRO à Sales and Distribution à Sales à Sales Document à Sales Scheduling Agreements with Delivery Schedules à Control EDI Inbound Processing à Define Special Features for Delivery Schedules

1.2.png

1.3 Assign Company Code

For each EDI partner, you assign the company code (that contains the payable to be posted) to the name for the invoice recipient in the EDI invoice.

Financial Accounting à Accounts Receivable and Accounts Payable à Business Transactions à Incoming Invoices/Credit Memos à EDI à Assign Company Code for EDI Incoming Invoice

1.3.png

1.4 Enter Program Parameters

For each EDI partner and invoice company code, you enter parameters for the content and the procedure, which determine how the EDI invoices are posted in the system.

Financial Accounting à Accounts Receivable and Accounts Payable à Business Transactions à Incoming Invoices/Credit Memos à EDIà Enter Program Parameters for EDI Incoming Invoice

1.4.png

1.5 Assign Tax Codes

For each EDI partner, you assign the tax code defined in the SAP System to the tax type and the tax rate determined by that partner.

Financial Accountingà Accounts Receivable and Accounts Payable à Business Transactionsà Incoming Invoices/Credit Memos à EDIà Assign Tax Codes for EDI Procedures

1.5.png

1.6 EDI Configurations

Transaction Code: WE20

1.6.1 Output Type LPET

Outbound Configuration

Basic Type: DELFOR01

1.6.1.1.png

Inbound Configuration

1.6.1.2.png

1.6.2 Output Type LAVA

Outbound Customizing

Basic Type: DESADV01

1.6.2.1.png

Inbound Customizing

1.6.2.2.png

1.6.3 Output Type RD04

Outbound Customizing

Basic Type: INVOIC01

1.6.3.1..png

Inbound Customizing

1.6.3.2.png

2 Condition Records

2.1 Create Customer-Material Info Record

Transaction Code: VD51

Must 18 characters customer material number.

2.1.png

2.2 Create Output Condition Record for Purchase Schedule Agreement

Transaction Code: MN10

Output Type: LPET

2.2..png

2.3 Create Output Condition Record for Outbound Delivery

Transaction Code: VV21

Output Type: LAVA

2.3.png

2.4 Create Output Condition Record for Billing Document

Transaction Code: VV31

Output Type: RD04

2.4.png

2.5 Master Data

Transaction Code: BP

You must enter Partner Description in step 1.1. purchase schedule agreement into Partner Description.

2.5.png

Note: Must enter supplier number into Acct at cust. (KNVV-EIKTO) field.

3 Process Step

3.1 Create Purchase Schedule Agreement

Transaction Code: ME31L

Agreement Type: LP

3.1.png

3.2 Create Sales Schedule Agreement

Transaction Code: VA31

Agreement Type: LP

3.2.png

3.3 Add new schedule line in Purchase Schedule Agreement

Transaction Code: ME38

3.3.1.png

When add new schedule line, output which LPET is trigger automatically. After that IDOC which basic type is DELINS is created for output and input.

3.3.2.png

Note: The system checks M_VLPMA table for matching sales and purchase schedule agreement document.

After this step sales schedule agreement will be update automatically.

3.3.4.png

3.4 Create Outbound Delivery

Transaction Code: VL01N

3.4.1.png

When delivery is posted goods issue, LAVA output triggered automatically.

3.4.2.png

IDOC which is created automatically by the reference of outbound delivery, triggered inbound delivery in the system.

3.4.3.png

3.5 Create Billing Document

Transaction Code: VF01

3.5.1.png

Finally, RD04 output is triggered automatically and MM invoice is created automatically screenshot is like below.

3.5.2.png

3.5.3.png