Valhalla – Sweden / Denmark

The main objective of this project is to implement 2 new plants (SE/DK) to the existing business process
in Europe SAP system (ERM to ERP).

Below are the Org. Structure details:

Plants:

SE01 – Partner Number: BALANS

DK01 – Partner Number: C5

Purchase Organization:

SE00

DK00

Company Code:

SE11

DK11

Below are the Interfaces used for Valhalla Project:

1. Material Master – Existing Interface – Logical Message: ZMATMAS and Partner Number: C5 /
BALANS (Outgoing IDOC)
2. PO – New Interface – Logical Message: ZPORDCR1 and Partner Number: C5 / BALANS (Incoming
IDOC)
3. PO Ack – Existing Interface - Logical Message: ORDERS and Partner Number: C5 / BALANS
(Outgoing IDOC)
4. GR – Existing message Type used with our own functional module - Logical Message:
ZGRINBNDDELVRY and Partner Number: C5 / BALANS (Incoming IDOC)
5. Stock movement – Existing Interface - Logical Message: ZTRANSPOST and Partner Number: C5 /
BALANS (Incoming IDOC)
6. Stock Picture – Existing Interface - Logical Message: ZSTOCKPICT and Partner Number: C5 /
BALANS (Incoming IDOC)
7. DESADV - Existing Interface with few changes in the logic specific to SE/DK - Logical Message:
DESADV and Partner Number: CUS01(Incoming IDOC)

PO & PR Document Types:

ZNB – Standard process

ZRL – Return Scenario’s

Below are the different ICO scenarios used as part of Valhalla Project:

ZNB:

BE to SE/DK
DE to SE/DK

UK to SE/DK

MX to SE/DK

US to SE/DK

SE to DK (or) DK to SE

ZRL:

SE/DK to BE

SE/DK to DE

SE/DK to UK

SE/DK to MX

SE/DK to US

SE to DK (or) DK to SE

In Return process we have again different sub scenarios in each flow:

1. With FG material –PIR with Price and no acc. Assignment category – Return tick will be selected
automatically and no Free items tick
2. With Pallet Material– If PIR has price, only return tick will be there else both Return and Free
items indicator will be ticked – Account Assignment Category “Y”
3. With Keg Material- If PIR has price, only return tick will be there else both Return and Free
items indicator will be ticked – Account Assignment Category “Y”

Below is the detailed explanation about each process/scenario with screenshots:

1. PO & PO Ack:

Normal Scenario – ZNB : 3PL will place the XML file with relevant information like Company
Code, Plant, Pur. Grp, Material, Storage Location, Qty, 3PL PO number(header->communication
tab->Our reference)..etc then the file will reach PI system and PI system will convert the file into
IDOC and post into SAP successfully. Once IDOC successfully posted and PO is created lly PO Ack
will be triggered to 3PL from SAP with relevant information like SAP PO, 3PL PO, IDOC status
53..etc.

Note: If PO is having FG materials lly we will have line Item 11 with Keg materials where we have
maintained Sales BOM, Packaging Instructions. In Normal ZNB Process, all Sales BOM’s will have
Price maintained PIR else entire PO idoc will get failed.

PO IDOC:
SAP PO:

PO Ack:
Return Scenario – ZRL:

 With FG material –
PO:
PO Ack:
 With KEG/Pallet Materials –
PO with Price:

PO Without Price:

PO Ack:
 2. Goods Receipts: 3PL will place the XML with SAP PO, Storage Loc., Plant, Batch ID, Qty, UOM and
Posting date/Manf. Date and Expiry Date.

Note: If the GR is belonging to BE/UK/Germany flow, 3PL has to send GR XML with SAP batches (3PL and
SAP batches should be matched) and for US/MX flow 3PL has to send any batch (with Manf. Date and
Expiry date) which is not available in SAP as well so that auto batch creation will works at that time
SAP GR:
 3. DESADV(US/MX) Flow(IDOC status 52): Here there will be no 3PL involvement as this will be done
by Connect team. Connect team will place the IDOC by changing PO line item qty information via
Sales Order in the IDOC.(Partner Number – CUS01). Usually, DESADV will create I/B delivery for
other countries not for Se/DK specifically. But corresponding SO info will not get changed.

IDOC:

SO displayed in above IDOC:

4. Purchase Requisition for SE/DK: PR’s will come into picture when 3rd party process will be
required and PR will not be created for ICO scenario’s. Here no 3PL involvement is not required
and PO will be created Manually w.r.t PR in SAP. Once SAP PO is created, we have inform to 3PL
team to create 3PL 3rd party PO w.r.t SAP PO. Then 3pL will create 3PL PO and will send GR XML
w.r.t SAP PO(only GR Interface will be required).

Once PR is created, automatically Workflow will be triggered for approval(2 levels of approvals Z1 and
Z2 release codes) Leve 1: Christophe(Christophe.Stevens@ab-inbev.com) and Level 2:
Renaut(renat.shamsutdinov@ab-inbev.com)
 Note: Detailed data available in FD.
PR:

PO:

5. Stock Movement: 3PL will place the XML file with below diff. Movement types to move the stock
from one s.loc to other S.Loc and reverse the same(344 & 343) / Scrapping of goods and reverse
the same (552 & 551)/ issue goods to cost center and reverse the same(202 & 201)/ one material
to other material(311).

Note: If you are moving the stock from 1000 s.loc to 4000 s.loc, but in IDOC STGE.LOC will be 4000 and
Move_StLoc will be 1000 as per the mapping. Below is the sample screenshot of 344 & 343 movement
type(1030 to 1000 s.loc):