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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
This entry point is used to take over upon sub-contract order deletion just before deleting the EO header.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
This entry point is used to take over upon sub-contract order deletion just before deleting a released product.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
This entry point is used to take over upon sub-contract order deletion just before deleting the Service.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
This entry point is used to take over upon sub-contract order deletion just before deleting a component.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is an open log file
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.
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 |
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).
There is one transaction in progress.
Activating the GPE variable allows to avoid the standard control.
There is an open log file
The [F:ITM], [F:ITF] buffers are loaded at the moment of the entry point call.
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 |
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.
There is one transaction in progress.
Activating the GPE variable allows to avoid the standard control.
There is an open log file
The [F:ITM], [F:ITF] buffers are loaded at the moment of the entry point call.
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 |