ZMATVENDOR
- ZMATVENDOR: is an ‘Exception table’ that is stocked in BW
- It contains Material x Vendors duplets
- It is used to identify intra-GBU flows that would otherwise be considered inter-GBU by BW algorithm.
- Impact on: DiP files (FS / ITI / SOB)
This Matrix/table is used for not standard flow with unlinked Purchase Order and Sales Order
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
How it's fed
This ZMATVENDOR table was historically manually ‘on demand’ by BW team (or Jean-Christophe).
Now, it's automatically populated it on a daily basis
=> we could potentially have new lines everyday
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 here