Ansicht
Dokumentation

IDOC_INPUT_STOREORDER - NOTRANSL: VWWS-Interface: Input Storeorders (IDOC-ORDERS) Dipatcher

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Functionality

This function module is called by the SAP ALE inbound interface for automatic creation of store orders when order data arrives in the IDoc structures ORDERS or WGSREQ.

It can process both IDoc categories as inbound IDoc structures.

A parser is called to scan the IDoc structure. The parser analyzes the IDoc, starts application modules for each segment read to analyze the data, and after the purchase order has been completely read in, starts the module for posting the document.

If any processing errors occur, the parser - after it has been triggered again - is able to start processing the order items that were not previously posted.

The incoming orders can - depending on the content and Customizing settings - be converted to MM purchase requisitions or purchase orders.

Example

A store sends an order in the form of an ORDERS IDoc to R/3 in the head office. The order IDoc is passed on from the ALE layer to this module. The module passes the IDoc structure to the parser, which then reads the IDoc segments. First the header segments are read, then the item segments. Errors are recorded in a log. The correct items are converted along with the header to a purchase order/ purchase requisition.

Notes

• Several orders can be sent in the same IDoc.

• Codes such as ISO currencies are compulsory!

• Not all fields in ORDERS are processed. (see interfaces)

• Only segments are processed that contain required/optional fields.

• Only orders can be accepted for the target client (control record IDoc).

• Note: data is always converted in the converter (outside R/3)!

• Dates are always required in the format yyyymmdd !

• External documents numbers (as in R/3 external number assignment) is not supported. An external document number can be entered as a reference (e.g. for an order confirmation too).

• Fields containing no data are always filled with blank.

• The correct field length and type (e.g. date) is not checked. (Performance)

• If no vendor/supplying plant is available in the order item, the system runs supply source determination.

If the result is not unique, the first entry found is chosen (TOP-DOWN). If order items are transferred without a source of supply, and if adding different sources of supply to the items results in more than one purchase order document, the items are arranged as required and converted to documents. A vendor material number only makes sense as an item ID if the vendor was also transferred.

• The unit of measure must either be included in the transfer or be determined uniquely.

• For every item at least the quantity and the article identification (e.g. the EAN or the article number) must be contained in the IDoc.

• In Rel 1.1 you can either create purchase orders or purchase requisitions only.

• Schedule lines are sent as separate items.

• Prices/conditions are only determined in the central system.

• Only default account assignment categories are used

• (else AScat + acc.ass. data such as cost center...)

• If more than one item is sent for identification, the first correct item is used in the case of ORDERS, then the EAN, then the material number, then the vendor material number in the case of WGSREQ.

Further information

Parameters

APPLICATION_VARIABLE
CALL_TRANSACTION_DONE
IDOC_CONTRL
IDOC_DATA
IDOC_STATUS
INPUT_METHOD
IN_UPDATE_TASK
MASS_PROCESSING
RETURN_VARIABLES
SERIALIZATION_INFO
WORKFLOW_RESULT

Exceptions

ERROR_IN_MAPPING
WRONG_FUNCTION_CALLED

Function Group

WVFB

ROGBILLS - Synchronize billing plans   General Material Data  
This documentation is copyright by SAP AG.

Length: 4384 Date: 20240604 Time: 014653     sap01-206 ( 85 ms )