SUBSRHC processing: SUBSRHC
ALIPICSRH: Loading of the return detail after selection of a delivery line
This entry point is used to take over after each delivery detail selection in order to complete the loading of the [M :SRH1] screen class for the return detail.
It is called in the customer return management during the picking of shipments.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log file.
Different call cases
This entry point is called from customer return management for each selected delivery line in the delivery selection panel. If the complete delivery is selected, the entry point will be called for each line.
Warning: This entry point is not called when clearing a line.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…). It is usually the case for the file that contains the header but not for the file that contain the lines…
Table |
Significant content |
Table Title |
SDELIVERY |
Yes |
Delivery header |
SDELIVERYD |
Yes |
Delivery line |
SRETURN |
No |
Return header |
SRETURND |
No |
Return detail |
SORDER |
No |
Order headers |
SORDERQ |
No |
Order line quantities |
SORDERP |
No |
Order line prices |
BPARTNER |
No |
BP |
BPCUSTOMER |
No |
Customers |
BPDLVCUST |
No |
Ship-to customers |
ITMMASTER |
No |
Products |
ITMSALES |
No |
Products - Sales |
|
|
|
ALISDHSRH: Loading of return header after delivery picking
This entry point is used to take over after the picking of a delivery when loading the return header screen from the delivery header.
It is called in the customer return management during the picking of shipments.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log file.
Call context
This entry point is called in customer return management, when picking a delivery or a delivery line and no detail line exists yet for the return. The entry point is therefore called once for the return.
Warning: This entry point is not called when clearing a line.
Available variables and masks
The return object masks are open, the fields concerning the return header are loaded with the delivery header data. The fields concerning the first detail line are not yet loaded in the line grid.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…). It is usually the case for the file that contains the header but not for the file that contain the lines…
Table |
Significant content |
Table Title |
SDELIVERY |
Yes |
Delivery header |
SDELIVERYD |
Yes |
Delivery line |
SRETURN |
No |
Return header |
SRETURND |
No |
Return detail |
SORDER |
No |
Order headers |
SORDERQ |
No |
Order line quantities |
SORDERP |
No |
Order line prices |
BPARTNER |
No |
BP |
BPCUSTOMER |
No |
Customers |
BPDLVCUST |
No |
Ship-to customers |
ITMMASTER |
No |
Products |
ITMSALES |
No |
Products - Sales |
|
|
|
REAJUST: Re-adjustment of the quantity to return in SAL
This entry point is used during the picking of a delivery line in customer return management.
It is used to take over when selecting a delivery detail in order to readjust the quantity to return calculated in SAL.
It is called in the customer return management during the picking of shipments.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log file.
Call context
This entry point is called from customer return management for each selected delivery line in the delivery selection panel. If the complete delivery is selected, the entry point will be called for each line.
It is located in the $SEL1 label of the SUBSRHC processing after reading the delivery line and determining the quantity to return.
After the determination of the quantity to return in STK, the system converts this quantity in SAL. If the converted quantity differs from the converted quantity rounded based on the decimal number of the SAL, the system forces the SAL with the STK. The entry point is used not to force the SAL with the STK and to keep the delivery line SAL.
Available variables and masks
The [F:SDH] class is on line and loaded with the header of the delivery to return.
The [F:SDD] class is on line and loaded with the line of the delivery to return.
The [M:SRH0], [M:SRH1], [M:SRH2] return header screen classes are loaded.
The [M:SRH1] return line screen class is being loaded. The NOL variable contains the index of the line being loaded.
[M:SRH1]SAU(NOL) is loaded with the SAL.
[M:SRH1]STU(NOL) is loaded with the STK.
[M:SRH1]SAUSTUCOE(NOL) is loaded with the SAL-STK convertion coefficient.
The LQTYSTU variable contains the quantity to return in STK.
The WQTY variable contains the quantity to return converted to SAL and rounded.
The WQTYSAU variable contains the quantity to return converted to SAL and not rounded.
If WQTY <> WQTYSAU the system forces the SAL with the STK.
To avoid forcing the SAL with the STK, it is necessary to act on the WQTYSAU local variable.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…). It is usually the case for the file that contains the header but not for the file that contain the lines…
Table |
Significant content |
Table Title |
SDELIVERY |
Yes |
Delivery header |
SDELIVERYD |
Yes |
Delivery line |
SRETURN |
No |
Return header |
SRETURND |
No |
Return detail |
SORDER |
No |
Order headers |
SORDERQ |
No |
Order line quantities |
SORDERP |
No |
Order line prices |
BPARTNER |
No |
BP |
BPCUSTOMER |
No |
Customers |
BPDLVCUST |
No |
Ship-to customers |
ITMMASTER |
No |
Products |
ITMSALES |
No |
Products - Sales |
|
|
|