Importing delivery requests enables the creation of new requests or the modification of those delivery requests associated with a contract line. Certain lines can also be deleted, if required.
A delivery request refers to an already existing contract line.
A delivery request refers to a contract or a product that must already exist.
The main file to be set up remains the SORDEC file (contract line). Indeed it is the file linked to the SOQ object.
It is therefore necessary to set up two indicators, one indicator for the SORDERC file, and another indicator for the SORDERQ detail file.
During an import, the existence of the main object (contract line) is recognized automatically by means of the main key representing the contract number, and the line number (SOHNUM + SOPLIN).
The identification of the existence of the detail lines is made, if they exist, in two ways as a function of the presence or not of the quote line number in the import template :
If two lines have the same delivery date, it is necessary to set up the line number in order to differentiate them. If this is not done, it is always the first line corresponding to the search criteria that will be processed.
The sequencing field (CAD) needs to be set up in order to properly integrate daily, weekly and monthly requests. This represents a special case because this field in neither entered not displayed in a standard management mode. Conversely, this is a necessary operation to be able to differentiate between the various types of requests. If the field is no longer present in the template or its value is equal to zero, the system will consider that it is a daily request.
The "Delivery request" import deals with the deletion of a line. A request is deleted if it is imported with an ordered quantity set to "0".
The following tables are used by the function. Their content must be updated if necessary :
Table |
Table description |
---|---|
SALESREP [REP] |
|
SORDERC [SOC] |
Sales orders - early / late |
SORDERQ [SOQ] |
Sales orders - quantities |
(*) In some management cases, a contract line being recognized may not depend on the contract line number. In that case, the system makes it possible not to enter these pieces of information. Yet the information provided must make it possible to clearly identify a contract line. In case of uncertainty, the system rejects the import.
The alternate solutions are:
This template can be used in import and export modes. The data is updated in the following tables :
Table |
Table description |
---|---|
BPARTNER [BPR] |
|
BPCUSTMVT [MVC] |
Customer transactions |
BPCUSTOMER [BPC] |
|
BPDLVCUST [BPD] |
|
FACILITY [FCY] |
|
ITMBPC [ITU] |
|
ITMFACILIT [ITF] |
|
ITMMASTER [ITM] |
|
ITMMVT [ITV] |
Product-site totals |
ITMSALES [ITS] |
|
ITMWRH [ITW] |
|
SORDER [SOH] |
|
SORDERC [SOC] |
Sales orders - early / late |
SORDERP [SOP] |
Sales orders - price |
SORDERQ [SOQ] |
Sales orders - quantities |
TABSOHTYP [TSO] |
|
TABUNAVAIL [TUV] |
|
WAREHOUSE [WRH] |