Subcontract orders
Use this function to customize the Subcontract orders (GESSCO) function to the needs of your organization and your processes.
Your system is provided with a standard or master Subcontract orders entry format. You can modify the master or create new entry formats to suit your processes, your users or just to make your system more convenient to use. Each format affects the way in which information is entered, displayed and printed.
You create each entry format as a Transaction. Each transaction you define is available for selection when the Subcontract orders function is selected from the menu. You are advised, however, to get a basic understanding of how your system works before changing the master format.
Prerequisite
Refer to documentation Implementation
Screen management
The Subcontract orders Entry transactions function contains a header information section and one tab per feature of the functionality:
- Header information. The header information contains the code and name for this entry transaction, and the user access code.
- Parameters. Use this tab to describe the functional characteristics of this entry transaction.
- Input. Use this tab to provide default entry, and display, fields and values.
- Analytical. Use this tab to define the default analytical dimensions applicable to this entry transaction.
- Documents. Use this tab to define which printed documents are required for this entry transaction.
Header
The header information provides key tracking and access information. The header information is displayed with each tab.
Each transaction code you define is available for selection when the Subcontract orders function is selected from the menu.
Subcontract order trans.
| Transaction (field PTRNUM) |
|
Code used to identify the transaction set up. The setup of the entry transactions enables the user to fully set up the entry screens associated with a document (quote, invoice order, request for quotes etc.) or with a stock transaction type (receipt, issue etc.). For each document or stock transaction type, it is possible to define as many entry transactions as necessary, each one being identified by a code. Each transaction is used to define, both for fields located on the document header and fields entered in the lines, whether they must be:
Upon validation of this setup, dedicated entry screens are created, and then can be used by any user having been granted rights on the access code defined on this setup header.
|
| Description (field DESAXX) |
|
Transaction description. |
| Active (field ENAFLG) |
|
Use this field to activate or deactivate a transaction. |
| Access code (field ACSCOD) |
|
This access code is used to restrict access to data by user or group of users. |
| Group (field GFY) |
|
The company or site group entered here is used to filter the entries. |
Tab Parameters
You use this tab to define functional characteristics for this entry transaction. This includes the following information:
- The default status of the subcontract orders
- The default entry processes to be available to the user such as material allocations (global or detailed) and whether requirements are considered.
Use
| Transaction reserved for automatic generation (field TRSAUTO) |
|
This flag makes it possible to specify that the transaction is reserved for the automatic subcontract order generation functions. |
Authorized statuses
| Allow status (field SCOSTA) |
|
This field is used to specify the authorized status(es). |
Allocations
Requirement considered
Tab Input
You use this tab to provide default entry, and display, fields and values. Where fields can be entered or displayed you can select from the following values:
Entered
The associated field is to enable data entry.
Displayed
The associated field is to be displayed. It is not to be available for data entry.
Hidden
The associated field is not to be displayed.
Entry parameters
Release entry
Materials entry
| Storage site (field STOFCYCOD) |
|
Setup used to define if, for this entry transaction, the storage site corresponding to the site where the materials are made available, must be:
The default storage site corresponds to the order site. |
| field STOFCYSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Location (field LOCCOD) |
|
Parameter used to define, for this entry transaction, if the location must be:
|
| field LOCSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Lot (field LOTCOD) |
|
Parameter used to define, for this entry transaction, if the lot number must be :
|
| field LOTSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Major version (field ECCCOD) |
|
Use this field to control entry or modification of the Major version number for a product. You can set this field to one of the following values:
|
| field ECCSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Minor version (field ECCCODMIN) |
|
Use this field to control entry or modification of the Minor version number for a product. You can set this field to one of the following values:
|
| field ECCSCRMIN |
|
Specify, for this entry transaction, if the field must be present in:
|
Service entry
Tab Analytical
You use this tab to define the default analytical dimensions applicable to this entry transaction.
Block number 1
Released product entry
| field CCESCR |
|
Parameter invisible and not used. |
Grid Released product
| Dimension type (field DIE) |
|
You can enter an analytical dimension type code on each table line. |
| Method (field CCECOD) |
|
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
Material entry
| field CCESCR2 |
|
Parameter invisible and not used. |
Grid Materials
| Dimension type (field DIE2) |
|
You can enter an analytical dimension type code on each table line. |
| Method (field CCECOD2) |
|
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
Operation entry
| field CCESCR3 |
|
Parameter invisible and not used. |
Grid Operations
| Dimension type (field DIE3) |
|
You can enter an analytical dimension type code on each table line. |
| Method (field CCECOD3) |
|
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
| Preload dimensions |
|
Click the Preload dimensions action to load the default dimensions defined for a selected group of sites or companies. |
Tab Documents
You use this tab to define which documents to print with each subcontract order and the number of copies required.
You can also define whether a trace file and a provisional cost calculation is to be generated when the subcontract order is printed.
Subcontract documents
| Material issue slip (field DOCFLG) |
|
Click this check box if a Material issue note (BSM) must be printed. If a Material issue note is not required, leave clear. |
| Document (field DOCNAM) |
|
If the associated document check box is selected, enter the report code for the standard printed document. |
| Job ticket (field NPRFLG) |
|
Click this check box if a Job ticket (BONTRV) must be printed. If a Job ticket is not required, leave clear. |
| Document (field NPRNAM) |
|
If the associated document check box is selected, enter the report code for the standard printed document. |
| Technical sheet (field TECFLG) |
|
Click this check box if the Technical sheets (FICHTEC) must be printed. If the Technical sheets are not required, leave clear. |
| Document (field TECNAM) |
|
If the associated document check box is selected, enter the report code for the standard printed document. |
Provisional cost documents
| Provisional cost (field MCCIMPMOD) |
|
The provisional cost calculation is launched at the end of creation or modification of a subcontract order.
|
Reports
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.
Specific actions
|
Click the Validation action to save this entry transaction definition. This triggers the corresponding screens to be generated. A warning message is displayed suggesting that you view your results to check the display is as you expected. Should you need to make further adjustments click Cancel, adjust your definition and revalidate until the results you require are displayed. |
|
Click the Copy action to copy this entry transaction to a different folder. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
You do not have the access rights for this codeThis message appears when the access code entered does not exist in the user profile. To solve this problem, it is necessary to choose an access code from the list displayed or (provided you have the authorization) to add the requested access code to the user profile.
Report dictionary: XX Record does not existYou have chosen in the tab Documents a report reference that does not exist in the Report dictionary.
This screen is common to the entry transactions for the