Histórico da Página

CREQ_1508 - Stoppage Annotation

Request Features

Description

• Develop a production annotation method without needing to register all operations of the production order.
  This modality aims at enabling the production for the cases in which there is an operation that does not need to be controlled or has a very little execution time;
• Enabling the user to perform stoppage annotation, even if there are production annotations in the same period.
• Enabling the user to perform production annotation, even if there are production annotations in the same period.
• Remodel the annotation screen model 1 to improve performance.

Important

(Only for Microsiga Protheus, previous versions to version 12)

Before executing the compatibility tool, enter the  U_UPSFC008 :

• Make a backup of the product database that will run the compatibility tool (directory PROTHEUS_DATA\DATA, if version 10, or \PROTHEUS11_DATA\DATA, if version 11) and from SXs data dictionaries ( PROTHEUS_DATA_SYSTEMdirectory, if version 10, or  \PROTHEUS11_DATA\SYSTEM, if version 11).
• The directories mentioned above correspond to the standard installation of Protheus. Therefore, they must be changed according to the company installation environment.
• This routine must be run in exclusive mode, that is, no user must be using the system.
• If data dictionaries have customized indexes (created by the user), before running the compatibility tool, make sure they are identified by nickname. If the compatibility tool needs to create indexes, it adds from the original order installed in Protheus, which can cause overwriting if they are not identified by nickname.
• The compatibility tool must be run with the Referential Integrity deactivated*.

Attention

The procedure must be performed by a qualified professional as the Data Bank Administrator or equivalent!

The erroneous activation of the Referential Integrity drastically changes the relation among tables in the data bank. Therefore, before using it, note the procedures as follows:

1. In the Configurator (SIGACFG), check if the company uses Referential Integrity by selecting the option Integrity/Checking (APCFG60A).
2. If there is no active Referential Integrity, all the companies and branches registered for the system are listed in a new window and none of them is selected. In this case, AND ONLY IN THIS CASE, you do not need any other activation/deactivation integrity procedure; just finalize the checking the apply the compatibility tool according to instructions.
3.  If there is active Referential Integrity, a message in the Checking the relation among tables window is displayed in all companies and branches. Confirm message for checking conclusion or;
4.  If there is active Referential Integrity in one or more companies, not in its totality, all the companies and branches registered to the system are listed in a new window and only the one(s) that have integrity are selected. Note which company(ies) and/or branch(es) have activated integrity and reserve this note for later query in the reactivation (or, contact the Framework Help Desk for information in relation to a file that has this information).
5. In the cases described in the items iii or iv, AND ONLY IN THESE CASES, you must deactivate such integrity by selecting option Integrity/ Deactivate (APCFG60D).
6.  When the Referential Integrity is deactivated, run the compatibility tool, according to instructions.
7. After applying the compatibility tool, the Referential Integrity must be reactivated, IF AND ONLY IF it has been deactivated, through option Integrity/Activate (APCFG60). Keep information on company and/or branches that have integrity activation, by selecting and confirming the activation again.

Contact the Framework Help Desk IN CASE OF DOUBTS!

1. In  Microsiga Protheus TOTVS Smart Client (if version 10) or ByYou Smart Client (if version 11), enter  U_UPSFC008  in the field Start Program. Important: For proper update of the data dictionary, ensure that the compatibility program date is equal or later to 9/30/2015.
2. Click OK to continue.
3. After the confirmation is shown on screen to select the company where the data dictionary is modified.
4. Upon confirming, a warning message is displayed regarding backup and the need to run it under exclusive mode.
5. Click Process to start the processing. The first step of the execution is file preparation. 
   A explanatory message is displayed on screen.
6. Afterwards, a Finished updating window is displayed with all the processed updating history (log). In this updating log, only the fields updated by the program are presented. The compatibility program creates fields that do not exist on the data dictionary yet.
7. Click Save to save the log displayed.
8. Click OK to complete processing.

Compatibility Tool Updates

(Only for Microsiga Protheus, previous versions to version 12)

1. Creation or Change  of Questions in the file SX1 – Register of Questions:

2. Creation or Change (only keep the corresponding instruction) of Fields in the file SX3 – Fields:

• Table BGD - Prod x Cob x Proc x Co-Part:

Important:

The size of  the fields that have group can vary according to environment in use.

5.  Creation or Change of Indexes in the file SIX – Indexes:

Machine - SFCA002

To break the annotation, select the option "Break Annot" in the register of machine used by the script operation used in the production order.

Production Annotation - SFCA310/SFCA316

In the browser, the production annotation screen, both in model 1 and 2, when clicking F12, 3 new parameters will be displayed. 

• Treatment Workforce: Defines how the workforce of the production annotation is broken. It can be:
• Does not interfere: The Workforce annotation is in the first annotation without break of stoppage.
• Keeps hours: The Workforce annotation is broken in two(or more) annotations, keeping the amount of hours of annotation before the break/interval generated by the stoppage.
• Reduces Workforce: The Workforce annotation is broken in two(or more) annotations, reducing the amount of hours of stoppage interval.
• Treatment GGF: Defines how the workforce of the production annotation is broken. It can be:
• Does not interfere: The GGF annotation is in the first annotation without break of stoppage.
• Keeps hours: The GGF annotation is broken in two(or more) annotations, keeping the amount of hours of annotation before the break/interval generated by the stoppage.
• Reduces GGF: The GGF annotation is broken in two(or more) annotations, reducing the amount of hours of stoppage interval.
• Scrap Treatment: Defines how the scrap of the production annotation is broken. It can be:
• Proportional: Divides the amount of scraps proportionally by the amount of hours executed per each new annotation generated by the break.
   
• Keeps first: The scraps are all entered in the first annotation.
• Keeps last: The scraps are all entered in the last annotation.

The production annotation must be regularly registered, if there is a stoppage between the start and end time of annotation, the break is automatically executed according to the rules of parameters above.

Stoppage Annotation - SFCA311

The stoppage annotation must be regularly registered, if there is a stoppage between the start and end time of annotation, the break is automatically executed according to the rules of parameters above the production annotation.

The break of Production Annotation only will happen if it overlaps all the stoppage annotation, that is, the start time of production must be earlier than the beginning of the stoppage and the end time of the production must be higher than the stoppage end. If the rule is not respected, a message informing that there is production/annotation production entered in this date.