CRESIHBETFCY: Possibility to create intersite invoices

Use this entry point to act in invoice entry in order to allow intersite invoice entry.

It is called upon entry control of the SALFCY (sales site) and BPCINV (invoice customer) fields in order to short-circuit the intersite invoice entry control.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

It is called in invoice management upon entry of SALFCY and BPCINV fields. It is located in the actions after modifying the AM_SALFCY and AM_BPCINV fields. It is located after the determination of the BETCPY (intercompany) and BETFCY (intersites) flags of the invoice, before the control of these 2 flags to prohibit the entry if BETCPY=1 and BETFCY=2 (Intersite invoice). The EP is set so as to prevent the control.

Available variables and masks

The screen classes of the invoice object are available (SIH0  SIH1  SIH2  SIH4 (lines) SIHV)

In AM_SALFCY, VALEUR contains the value of the SALFCY field. In AM_BPCINV, VALEUR contains the value of the BPCINV field.

[M:SIH1]BETCPY=1: The invoice is intracompany

[M:SIH1]BETFCY=2: The invoice is intersite

WPE_CRESIHBETFCY is a variable initialized to 0. It must be set to 1 by the EP in order not to carry out the control and to continue the entry of the intersite invoice.

Open tables

The tables of the invoice object are open.

In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file that contains the header but not for the file that contain the lines…