ZMATVENDOR

• ZMATVENDOR: is an ‘Exception table’ that is stocked in BW
• It contains Material x Vendors duplets

• It is used to exclude some purchase flows from ‘External Purchase Order’, which are in reality ‘Internal Purchase Orders’ (IPO).
• Impact on: BW DiP files : BW_EPO (EPO = External Purchase Orders)

Automation ZMATVENDOR:  done but will not be active before BW Freeze 

This Matrix/table is used for not standard flow, sometimes called 'Unlinked flows' (i.e., with unlinked Purchase Order and Sales Order). For standard flows, it's not used. More info about Specific flows rerfer to Dynasys - DiP-PP Specific flows analysis

How it's fed

This ZMATVENDOR table was historically manually ‘on demand’ by BW team.

Now, it's automatically populated it on a weekly basis with program ZBW_DYN023.

For more information, please check ZMATVENDOR specification.

In the medium term, the idea will be to add visibility to DiP team/Key users of its content: 

            => How: Export table’s content into a new .csv file so that DiP team can check the  content with users. We would need to add a column 'GBU' (GBU of the Material, which is not the GBU of Material x Plant but it's good enough) so that it can be checked quickier

The automation was done by Ismail Ammor on BW side, and coordinated by JC/Pablo on SAP/Dyn side. More info on spec - STO Lifetime and Dynasys files populated

Use

As said above, this Matrix/table is used for not standard flow, sometimes called 'Unlinked flows' (i.e., with unlinked Purchase Order and Sales Order). For standard flows, it's not used.

It will affect the content of the following BW DiP information: Firm shipment, In transit, External Purchase Orders, Sales Order Book (so, files BW_ITI, BW_FS..., BW_EPO and BW_SOB).

For Not Standard SAP flows or 'Unlinked flows', it's common to have a Purchase Orders on the Receiving Site attributed to a "Solvay" Vendor (but without knowing the real Shipping Site), and a Sales Order from the Shipping Site to a "Solvay" Customer (Shipto).

In standard BW algorithm, we would have :

> External PO on Receiving Site:

> Firm Shipment on Shipping Site

=> this will create a problem on DiP as we would double count the requirement when launching the DRP, where in fact we know that it corresponds to the same flow.

=> To avoid this kind of issue, we use the ZMATVENDOR exception table, to define the duplets Material x Vendor for which we would like to exclude them from External Purchase Order (EPO) file.

For a given Mat x Vendor in ZMATVENDOR, the PO will be treated as "Internal Purchase Order" (or IPO) rather than "External Purchase Order" (EPO). Why we want to see it as IPO: because we know that behind the "Solvay" vendor, we have in fact a Solvay shipping site

To see how the full process is materialized in SAP and in DynaSys, please see below:

SAP process vs Dynasys data:

• The receiving site is placing a Purchase order in SAP with a Solvay Vendor code - At this stage we have nothing in Dynasys but we can display this information as "Internal Pruchase Order".

• The Shipping site will create a Sales Order in SAP once they received the PO with a Solvay customer code - At this stage we have data under "Firm Shipment" field

=> It is relevant to have Sales Order created regularly in SAP

• The shipping site will make the GI - At this stage the Firm Shipment is becoming an In-Transit

=> We take the Outbound Delivery to define the In Transit receipt date in Dynasys