Ansicht
Dokumentation

OALE_DSTSCN_DSALCSHP - Separate Sales and Shipping

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

This section of the IMG contains a description of the settings required for the Separate sales scenario in connection with Transfer between distributed systems.

Only those settings required in addition to the scenario Transfer between distributed systems are included.

Consistency Check

The function in this section checks the consistency of your settings. We recommend that you make use of the consistency check when you make your settings.

Execute the function in the sales system. This allows you to check whether the settings between the systems are correctly maintained for the required message types. Check the application consistency for the delivery system and the 'ORDERS' message.

To perform the consistency check, you have to create a variant for the RBDMMSD1 and RBDSDMM1 reports.

If you double-click on a line in the consistency check log, you will enter the corresponding Customizing transaction and you can make the necessary settings here.

Before you can do this, you have maintained the partner profiles in all the relevant systems.

Example

In this scenario, purchase orders should be created automatically when

In this scenario, purchase orders should be created automatically when sales orders are created in the remote sales system, and these purchase orders should be sent to another shipping system.

Both third-party orders (delivery from the other shipping system directly to the customer) and standard orders (delivery to the remote sales system) are supported.

The purchase order is then created automatically if the ALE indicator is maintained in the item category. This is the case for the item categories that are supplied by SAP as the standard for distribution.

Examples of item categories in the standard system are:

• For third-party orders,,ALES

• For standard purchase orders,,ALEN.

You can also set the ALE indicator for your own item categories. You do this in the Implementation Guide in the section Sales and Distribution -> Sales -> Sales documents -> Sales document item -> Define item category.

The decentral sales system can invoice the customer when the shipping notification has been sent from the shipping system to the sales system. If the shipping notification does not get sent (because of the Customizing settings), then customer does not get invoiced until the internal invoice has been sent.

Customizing in Remote Sales System

Determining Purchase Order Dates

So that the purchase order can be created automatically, the purchasing organization used, the purchasing group and order type must be maintained. You will need to maintain the vendor only if you allocate just one shipping system to the sales system.

This is done in the sales organization maintenance. For more information on this, please refer to the Implementation Guide: Corporate structure -> Definition -> Sales and Distribution -> Create sales organization.

Starting Billing (only for the third party case ALES)

So that billing in the remote system is carried out after the delivery by the shipping system, shipping notification must be sent from the shipping system to the remote sales system. In inbound processing, a goods receipt must be created automatically for the purchase order.

To make this possible, the plant, the storage location and the movement type for the goods receipt is determined for each sales organization. That is also carried out in sales organization maintenance

If you want the goods receipt to initiate billing, you must make settings for the pair "order type; position type" so that the billing quantity is equal to the goods receipt minus the quantity already invoiced. For more information on this, please refer to the Implementation Guide of Sales and Distribution in the section: Invoicing -> Invoices -> Define document flow for invoices. If you perform the function, choose Copy control: Sales document according to invoice in the pop-up window.

Message Control

The forwarding of the order confirmation to the customer can be set up via the message control. You use the message type BA00 to do this. In this case, the confirmation is only dispatched in the standard system if all the schedule lines of the sales order have been confirmed by the shipping system.

Error Processing

If errors occur during the automatic creation of purchase orders or changing of purchase orders, a work item is generated.

The standard tasks listed below must be assigned to positions or workflow organizational units.

Standard task: ID code	Description
SD_PO_Err	Error: Purchase order not created
SD_PO_ChgErr	Error: Purchase order not changed

Settings in Remote Purchasing System

If you want to assign more than one shipping system to the sales system, there must be purchasing information records present in the master data of the purchasing system. For each material you can decide on a shipping system by allocating a fixed vendor (= shipping system) to a material master record.

By using a Customer Exit in the SDALE001 enhancement, it is possible to allow several vendors for a material.

Settings in Central Sales and Shipping System

Message Control

MM Customizing

For a third-party deal, the remote sales system can obtain information on the delivery to customers via a shipping notification. To do this, set up message control for the delivery in the shipping system in such a way that the shipping notification is sent to the sold-to party, instead of to the ship-to party.

The following are used as message types:

Message	Message type
Shipping notification	LALE(to sold-to party)

Master Data and Control Data

For this scenario, the following master data must be distributed to all participating systems:

• Material master

• Customer master record

Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 7091 Date: 20240523 Time: 195935     sap01-206 ( 135 ms )