Process SCOLIB: SCOLIB
CRESCOMAJ: Update of custom/specific fields in EO header
This entry point is used to insert additional logic in the creation of sub-contract orders just before entering the EO header(this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The buffer [F:SCO] is loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
No |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CRESCIMAJ: Update of the released product specific/custom fields of the EO
This entry point is used to insert additional logic in the creation of sub-contract orders just before writing a released product (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO] and [F:SCI] buffers are loaded at the moment of the entry point call.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CRESCSMAJ: Update of the service specific/custom fields of the EO
This entry point is used to insert additional logic in the creation of sub-contract orders just before writing a Service (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCS] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
Yes |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CRESCMMAJ: Update of the component specific/custom fields of the EO
This entry point is used to insert additional logic in the creation of sub-contract orders just before writing a component (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
Yes |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
UPDSCOMAJ: Update of custom/specific fields in EO header
This entry point is used to insert additional logic in the modification of sub-contract orders just before reentering the EO header (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The buffer [F:SCO] is loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
No |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
UPDSCIMAJ: Update of the released product specific/custom fields of the EO
This entry point is used to insert additional logic in the modification of sub-contract orders just before rewriting a released product (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO] and [F:SCI] buffers are loaded at the moment of the entry point call.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
UPDSCSMAJ: Update of the service specific/custom fields of the EO
This entry point is used to insert additional logic in the modification of sub-contract orders just before rewriting a Service (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCS] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
Yes |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
UPDSCMMAJ: Update of the component specific/custom fields of the EO
This entry point is used to insert additional logic in the modification of sub-contract orders just before rewriting a component (this allows, for example, the initialization of the custom/specific fields).
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
Yes |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
DELSCOMAJ: Update of custom/specific fields in EO header
This entry point is used to take over upon sub-contract order deletion just before deleting the EO header.
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The buffer [F:SCO] is loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
No |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
DELSCIMAJ: Update of the released product specific/custom fields of the EO
This entry point is used to take over upon sub-contract order deletion just before deleting a released product.
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO] and [F:SCI] buffers are loaded at the moment of the entry point call.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
DELSCSMAJ: Update of the service specific/custom fields of the EO
This entry point is used to take over upon sub-contract order deletion just before deleting the Service.
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCS] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
Yes |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
DELSCMMAJ: Update of the component specific/custom fields of the EO
This entry point is used to take over upon sub-contract order deletion just before deleting a component.
Context and operating mode
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM] buffers are loaded at the time of the call to the entry point.
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
Yes |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CRESCKMAJ: Update of the Tracking specific/custom fields of an EO
This entry point is used to insert additional logic in the update of sub-contract orders just before writing a tracking in SCOTRK (this allows, for example, the initialization of the custom/specific fields).
Context and operating method
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM]], [F:SCS],], [F:SCK] buffers are loaded at the time of the call to the entry point (based on the current tracking).
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
UPDSCKMAJ: Update of the Tracking specific/custom fields of an EO
This entry point is used to insert additional logic in the update of sub-contract orders just before rewriting a tracking in SCOTRK (this allows, for example, the initialization of the custom/specific fields).
Context and operating method
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM]], [F:SCS],], [F:SCK] buffers are loaded at the time of the call to the entry point (based on the current tracking).
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
DELSCKMAJ: Update of the Tracking specific/custom fields of an EO
This entry point is used to insert additional logic in the update of sub-contract orders just before deleting a tracking in SCOTRK (this allows, for example, to delete specific data).
Context and operating method
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file
Available screen and file classes
The [F:SCO], [F:SCI], [F:SCM]], [F:SCS],], [F:SCK] buffers are loaded at the time of the call to the entry point (based on the current tracking).
The screen class [M:SCOK] linked to the automatic update of EOs is loaded.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CTLDLVFLG: Control of sold/deliverable materials
This entry point is used to insert additional logic in the creation/update of sub-contract orders in order to avoid controlling that the materials are sold or deliverable for the components made available to the sub-contractor (necessary to use shipments of materials to the sub-contractor's location).
Context and operating method
Transaction
There is one transaction in progress.
Activating the GPE variable allows to avoid the standard control.
Log file
There is an open log file
Available screen and file classes
The [F:ITM], [F:ITF] buffers are loaded at the moment of the entry point call.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |
CTLITMSTA: Control active, non expired product
This entry point is used to insert additional logic in the creation/update of sub-contract orders in order to avoid controlling that the product is active and is not expired.
Context and operating method
Transaction
There is one transaction in progress.
Activating the GPE variable allows to avoid the standard control.
Log file
There is an open log file
Available screen and file classes
The [F:ITM], [F:ITF] buffers are loaded at the moment of the entry point call.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (...).
Table |
Significant content |
Table Title |
SCOHEAD |
Yes |
E0 header |
SCOITM |
Yes |
Released products |
SCOSRV |
No |
Service |
SCOMAT |
No |
Materials |
ORDERS |
No |
WIPs |
BOM |
No |
BOMs |
BOMD |
No |
BOM lines |