ISSQLYCTL: Issuing the allocated stock submitted for a quality control

Use this entry point to authorize the issue of allocated stock lines that are the object of an analysis request.

During an order delivery or a WO tracking, the stock allocated to the order or to the WO and subject to an analysis request can therefore be taken into account and becomes deliverable or consumable.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the ALLSTOSORW sub-program of the STKSOR processing.

It is called during the loading of the stock to be issued (in the work screen STOSORW) from the detailed allocations of the source document (sales order or WO).

 To authorize that the stock lines subjected to a quality control are taken into account, it is necessary to load the [M :ALP]PECQLYCTL screen variable as follows:  [M:ALP]PECQLYCTL =  2.

 The significant variables are:

[M:ALP]TRSTYP:     Transaction type (Local menu no. 704)

[M:ALP]VCRTYP:    Source document type (2=sales order, 10=WO)

[M:ALP]VCRNUM, VCRLIN, VCRSEQ:    Source document identification

[M:ALP]STOFCY:   Site

 [M:ALP]ITM:           Product

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…).

NEWFILSTA: Modifying the filter on the allocations

Use this entry point to replace the filter applied to allocations in order for instance to modify their processing order.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the ALLSTOSORW sub-program of the STKSOR processing.

It is called during the loading of the stock to be issued (in the work screen STOSORW) from the detailed allocations of the source document (sales order or WO).

To replace the filter applied in standard to the allocations, the following actions need to be performed:

- Rewrite the filter:       Filter [STA] Where VCRTYP=[M:ALP]VCRTYP & VCRNUM=[M:ALP]VCRNUM &

&                  VCRLIN=[M:ALP]VCRLIN & VCRSEQ=[M:ALP]VCRSEQ &

&                  ITMREF=[M:ALP]ITMREF & evaluate(WFILSTA)

        by adding a sort order (Order By) for example

- Load the GPE variable as follows:  GPE = 1

The significant variables are:

[M:ALP]TRSTYP:     Transaction type (Local menu no. 704)

[M:ALP]VCRTYP:    Source document type (2=sales order, 10=WO)

[M:ALP]VCRNUM, VCRLIN, VCRSEQ:    Source document identification

[M:ALP]STOFCY:   Site

 [M:ALP]ITM:           Product

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…).

PECALLSOW: Preventing the issue of some allocations

Use this entry point in order not to load stock lines allocated to a document (sales order or WO) during its processing (delivery or tracking).

During an order delivery or a WO tracking, the stock allocated to the sales order or to the WO can be considered not deliverable or not consumable.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the ALLSTOSORW sub-program of the STKSOR processing.

It is called during the loading of the stock to be issued (in the work screen STOSORW) from the detailed allocations of the source document (sales order or WO).

 To prohibit the use of an allocated stock line, load the GOK global variable as follows:  GOK = 0.

 The significant variables are:

[M:ALP]TRSTYP:     Transaction type (Local menu no. 704)

[M:ALP]VCRTYP:    Source document type (2=sales order, 10=WO)

[M:ALP]VCRNUM, VCRLIN, VCRSEQ:    Source document identification

[M:ALP]STOFCY:   Site

 [M:ALP]ITM:           Product

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…).

DOC_SOW: Transferring the data from a document line using the STOSORW storage sc

Use this entry point to transfer data from the entry screen of document line to the storage screen of issue data (STOSORW).

It is called in all the documents processing issue flows.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the RECH_STOCK label of the STKSOR processing.

It is called in all the documents processing the issue flows at the end of a new line entry when using the data entered to determine the stock to be issued.

If a stock line has been found, it is therefore possible to load the information entered in the document line into the issue storage screen STOSORW ([M :SOW]).

The variable containing the name of the document line entry screen is:

LABRMSK     = Document line entry screen in the form of: [M :XXX]    (Example: [M :SDH1] for the deliveries)

The indexes to be used in the screen grids are :

LNOL             = Index for the document line in the ‘LABRMSK’ screen

I                      = Index in STOSORW [M :SOW]

The significant variables are:

 [M :ALP]STOFCY    = Site

[M :ALP]TRSTYP     = Movement type (local menu no. 704)

[M :ALP]VCRTYP    = Document type (local menu no. 701)

[M :ALP]ITMREF      = Product

 Warning:

This entry point is only designed to manage new fields.

The standard content of the STOSORW screen must not be modified.

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…).

ALI_SHTSOW: Completing the characteristics of a shortage line

Use this entry point to complete the characteristics of a shortage line generated upon automatic determination of the stock to be issued.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the GENSTOSORW sub-program of the STKSOR processing.

It is called upon the loading of a shortage line into the STOSORW work screen.

It therefore can be used to complete the content of the shortage line of the [M :SOW] work screen indexed via the K local variable.

For example, to load an ‘A1’ shortage status into this line, the following instruction must be added:

            [M :SOW]STA(K) = ‘ A1’

The significant variables are:

[M:ALP]TRSTYP:     Transaction type (Local menu no. 704)

[M:ALP]VCRTYP:    Document type (Local menu no. 701)

[M:ALP]VCRNUM, VCRLIN, VCRSEQ:    Document identification

[M:ALP]STOFCY:   Site

[M:ALP]ITMREF:   Product

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…).

MOD_SORPAR: Modifying the automatic issue parameters

Use this entry point to intervene on some parameters of the automatic issue such as the quantity to be issued.

Context and operating method

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located at the beginning of the GENSTOSORW sub-program of the STKSOR processing.

For example, it is used to intervene on the quantity to be issued. 

The accessible parameters are:

- [M:ALP]QTY:  Quantity to be issued (in active stock unit)

- The fields in the section 1 of the ALLPAR setup screen are entered and accessible. Warning: any modification on these fields must be performed according to an informed decision.    

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…).

OUV_ALLPAR: Modifying the issue parameters

Use this entry point to intervene on some issue parameters when searching the stock from the stock elements entered on the document line.

Context and operating method

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the OUVSOR sub-program of the STKSOR processing. 

The accessible parameters are:

- [M :ALP]PECSCOLOC:     Authorizing the subcontractor locations                                (1=no / 2=yes)

                                               Default value = 1

- [M :ALP]PECPLFLOC:      Authorizing the locations awaiting put-away                (1=no / 2=yes)

                                               Default value = 2

- [M :ALP]PECQLYCTL:     Authorizing the stocks that are the object of an analysis request    (1=no / 2=yes)

                                               Default value = 2 (if order or WO), 1 for other documents

CHARGE_ALL_SOW: Loading specific fields

Use this entry point to retrieve specific fields from the allocation table (STOALL) upon loading of the STOSORW work screen from the allocations of a document line.

Context and operating method

Transaction

There is no transaction in progress.

Log file

No trace file is open.

Different call cases - Significant variables

This entry point is located in the CHARGE_ALL_SOW sub-program of the STKSOR processing.

It is called during the loading of the stock to be issued (in the work screen STOSORW) from the detailed allocations of the source document (sales order or WO).

 The significant variables are:

I corresponds to the STOSORW ([SOW]) mask line index being loaded. 

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…).