SBT Globe Solution

SBT

Globe Solution

Scan Based Trading – Definition

• SBT can be translated as a consignment done to the customer. But different from regular consignment the sales are recognized based on a file received from the customer that contains all the scan data at the point of sale. So sales are not recognized based on any counting or order created by customer, but it is based on scanned materials already sold to the consumers.

• Process can be divided in 3 main steps• Delivery to the customer• Scan Data (based on the materials sold to the consumers in the point of Sale)• Audit process (Count and Variance Calculation)

• Supplier (Nestle) owns inventory and supplier is paid for scanned product. Inventory ownership passes from Nestlé DSD and creates an Accounts Receivable balance for the retailer when items are scanned at the point of sale.

• Partners split shrink based on periodic or quarter/trimester audits . Trading partners agree to share shrink, authorized items, price, and promotions at onset of the relationship. Shrink doesn’t include accounted for spoils, damages or shortages

High Level Design – Facts and Decisions

• GLOBE Should not have negative stocks. Occurrences should be avoided and fixed as soon as possible.

• Shared UPC scenarios and audit by group of material (PL5/Class), does not provide accurate information needed in SAP.

• With current process, huge amount of messages would be created in the system, and information would not be accurate, creating possibilities of failures and even higher misalignments.

• Decision was taken to consolidate consignment stock position in a unique plant, but by group

of customers (SBT Group). This way, negative stock can be minimized and it is possible to consolidate the stock movements, creating less stress in the system.

• Any kind of split that need to be done will be based on the consignment stock position of the plant by SBT group, in order to avoid negative stocks.

• In business scenarios where stock balance by customer/ material is needed, information will be built in Visicom:

• Cycle counts are not received in SAP, and only impact Visicom on hand balance (Customer/material)• Variance research will be built once audit information is received, specifically for the time period and

customer (based on audit numbers) and will adjust stock in SAP.• The stock balance by customer/ material could have negative stocks, with no limitations, as it will be in

Visicom and not SAP.• Total stock position by customer/material (Visicom) and SBT Group/Material (SAP), will not match, due

to the reasons above (different transactions updates differently the stock positions)

Documents Flows

SBT Flow

Type Order Type Delivery Type Invoice

SBT Delivery

SBT Scan DataDebit

SBT BuybackTo Truck

SBT Scan Data Credit

Order Type ZSB1

Order Type ZSB2

Order Type ZSB3

Order Type ZSB4

Delivery Type LF

Invoice Type ZSB2

Delivery Type LR

Invoice Type ZSB4

Acum. Stock

Movement

631 + Single Plant and Batch/ Group Customer

Acum. Stock

Movement

632 + Single Plant and batch / Group Customer

Invoice Cancellation

ZSB5

Invoice Cancellation

ZSB6

For only Logical Return to warehouse, Manual document ZSB3 with item category ZSB8 should be used

SBT Delivery


SBT DeliveryOrder Type

ZSB1Delivery Type LF

• Documents based on the standard consignment Fill up Flow

• Documents ZSB1 and ZSB3 (SBT Delivery and Return) will have pricing but will not be relevant for credit check

• Listing will be activated, so for messages received from HH with a material not authorized the Idoc will fail.

• Statistical delivery to be prepared to consider this document type

• Customer master data will identify SBT customer (Customer Group 3 + new table), so HH will use a different order type in the inbound message to SAP.

• For only Logical Return to warehouse, Manual document ZSB3 with item category ZSB8 should be used.

SBT Delivery Return

Order Type ZSB3

Delivery Type LR

631 + Single Plant and batch / Group customer

632 + Single Plant and Batch/ Group Customer

SBT Delivery

• Goods movement from Truck to SBT consignment stock to be posted at time of settlement

• Once in consignment, stock will be consolidated in a single batch - DSDBATCH

• When consignment movement is done, the movement is posted to a single plant, and consolidated by SBT Group.. Reasons:

• This will avoid performance issue, with less movements in MH (more details in the scan data part)• Consignment stock grouped by plant will make negative stock less frequent, and in case of problems it

will be easier to adjust.• MH does not need the stock position by customer as the information is not accurate, so only the total

value would be enough.• Finance still have quantities for material ledger and cost calculation

•SAP will not have the detail of consignment stock per customer

•CAO need be calculated in outside SAP

•Fill up delivery, when needed will be sent to PCG and iControl

SBT Return - Buyback

SBT Scan Data – Credit /Debit


SBT Scan Data (Debit)

SBT Scan Data (Return / Credit)

Order Type ZSB2

Order Type ZSB4

Invoice Type ZSB2

Invoice Type ZSB4

• Scan Data will be received via EDI in SAP, creating debit (or credit) documents for customer as scan data is processed.

• In the first moment there will be no inventory movement, sales volumes will be updated as sales documents and billings are created.

• Regular pricing, no credit check / blocks (but part of the credit exposure), no material listing activated

• Listing is not activated, but material determination rule will be built based on the stock position for the SBT group, if material is not found, IDOC will fail and EDI reprocessing tool need to be used to reprocess the document.

• Price and promotions received in the scan data will be copied in statistical conditions and report need to be created for later review of the differences. Document will not be blocked due to price/promo differences.

Acum. Stock

Movement

Acum. Stock

Movement

SBT Scan Data – Stock Movement

• Stock movement will be created once a day based on all credit/ debit memos created, consolidated in just one plant and per EDI group. This will significantly reduce the number of transactions in SAP (from more then 10.000 to around 120 – header level)

• Single batch will be used for goods movement

• Stock consumption would not have a direct link to the sales document and to the “real customer” (material document would be posted with “SBTGroup customer #”)

• Consignment stock can go into negative (but should not be frequent). Configuration will be activated to avoid possible issues in the messages, and later, negatives may be fixed.

Credit/Debit docs

Billing

Credit/Debit docs

Billing

Credit/Debit docs

Billing

Consolidation Single plant by

group of customers

Stock Adjustment in

SOS

SBT Scan Data – Stock Movement

Billing

Billing

Billing


group of customers

Consignment Stock

Updated

Cust:123 SBT Group A1Plant: 4200Material 01 = 10Material 02 = 12Material 03 = 06

Cust: 234 SBT Group A1Plant: 4300Material 01 = 05Material 02 = 06Material 03 = 06

Cust: 345 SBT Group B5Plant: 4400Material 01 = 12Material 02 = 12Material 03 = 12

SBT Group A1Plant: 5000Material 01 = 15Material 02 = 18Material 03 = 12

SBT Group B5Plant: 5000Material 01 = 12Material 02 = 12Material 03 = 12

Listing and Material Determination• SBT group concept will be created in order to group the customers, and be used for material

determination and listings. Field Customer Group 3 will be used for the SBT group.

• Each SBT customer need to be associated to a SBT group

• Listings will be created based on the SBT group, using standard functionality• Used to determine the authorized materials for a SBT group• Rules should be created only by SBT Group, no exceptions should be maintained by customer, if

necessary, new group should be created.• Listing will be sent to HH, so materials that are not listed should not be included in the SBT delivery• “Standard Listing” is checked in the SBT delivery, but not in the Scan Data

• Material determination rules will be based on SBT group and consignment balance, using a new development/table to also support limited edition• EDI will create the Idoc with the UPC number• During Idoc processing, before Order creation, this new table will be used to determine the correct

material based on the UPC, and also split materials in cases of shared UPCs• Table will be built based on the consignment balance for the SBT group + material master information• If UPC is not found in the table, regular process for material determination will be done, if also not

found, Idoc will Fail, and the EDI reprocessing tool need to be used after the master data fix..

Listing and Material Determination• Below is a description of the process for material determination during EDI processing for the order

creation:

IDOC Created with UPC

Look Exceptions in tables 620/6212

MEAN Table3

Mat. Determ. From Basic code to correct variant

5

If fails goes to 3

If not found = FAILS - reprocess If found more than 1 with –

pick one

If fails, document created with basic

material* risk of negative

EDI Processing

Order Creation/ Save process

For the material found in step 3 get the UPC and look

% table

4If not found in the table – FAIL the

IDOC

Check if customer is active. Or

Duplicated Order

Idoc fails, Idoc Listed in theEDI reprocessing1

Comments:• Access 2 is for exceptions when

customer is using internal code. If material is found, we still need to go to the mean table to find the UPC code ZK, that is the one used for the % table in step 4.

• Access 3, currently when more than one if found, it raised an error, in the to be, it should not give the error, but just pick one material

• Access 4 should always be executed

Split Criteria Table• New program and table will be created to calculate and store split %.

• The program would get the information from the consignment balance and some additional information from material master.

• Table will have: • SBT group• SAP Material – PL5 and UPC will be brought from material master• Quantity / % PL5 and % UPC• Date

• This table will be used in the Scan Data processing to determine the material based on the UPC, and for the material split for shared UPC> It will also be used to split at material level the variance calculated by PL5 after variance research.

• % will be calculated based on the consignment stock position of the SBT groups• General number should be 105 SBT groups, each group with 350 materials.

• Daily* program will be executed to update % in this table, based on the consignment stock position, % will be per SBT group, one % for materials with the same PL5 and another % for same UPC.

Material masterConsignment

stock in Plants% table by SBT

Group/ PL5 /UPC+ =

Split Criteria Table

• % Calculated by PL5% will be used for CNA invoice creation• % Calculated by UPC% will be used to identify and split shared UPCs in limited edition scenario, as

“Limited Edition / PL5” may contain materials that don’t share UPC• Below an example of the table.

SBT Group

SAP Mat Class UPC Qty % PL5 % UPC

001 50001 A 799 20 40% 40%

001 50002 A 799 30 60% 60%

001 50003 B 701 70 70% 100%

001 50004 B 702 30 30% 100%

001 50005 C 703 25 100% 100%

… … … … … …

Consig. Stock Material Master Calc. based plant stock

+ Date to keep history, and old data deletion based on job variant

Limited Edition and CNA Invoice split rule

• Example: Scan data of 13 is received for UPC 123. This UPC is a limited edition, with 3 materials (A, B and C)

• Step 1: Have the calculated % as explained in the previous slide• Step 2: Split the quantity among the materials based on the % found• Step 3: Round the result (0.5)• Step 4: Calculate the difference and allocate the difference in the material with the highest stock

• This calculation will need to be performed during the order creation process (SBT Scan Data) ONLY for shared UPCs (in limited edition scenario) and when creating the CNA invoice .

• The only purpose of this split is to determine a valid material and avoid as much as possible negative stock.

• Performance issues may be expected during Scan Data creation.

Shared UPCs (Limited Edition) and CNA Invoice split rule

• Alternative for SBT Scan Data order creation:• SAP material is only determined in the user exit, when processing the Idoc. • Idoc does not contain the final SAP number.• This user exit need to be enhanced:

• Check table based on UPC and SBT group • If % table has more than one material for this UPC (UPC% <> 100%), apply % in the table to

split the materials, creating more than sales order line for the same segment of the Idoc.• If 100% use the material in the table.

• If material is not found in % tables, proceed with the regular material determination• If not found in the MEAN table, Idoc will fail.

Scan Data Received

Idoc Created

User Exit in the Idoc

processing

Order created /

split of lines

Idoc Processing for Mat. Det.

Create X lines

Look table to find the % to apply

Perform Calculation

Shared UPCs (Limited Edition) and CNA Invoice split rule

• Creation of the CNA Invoice (shrink)• Information will be received in SAP by PL5• Variance will be calculated by PL5• Once CNA document is triggered, %table is used to split the variance from PL5 to material.

SAP Calculation

by PL5

Look table to find the % to apply

Create docs with

materials

Variance is Calculated

Daily program to Upd table

Trigger CNA Invoice

Negative Stocks

• Negative stock will be activated only for consignment

• Single batch will be used so there is no need to enhance Dynamic Batch determination logic to work with negative stock

• Depending on the volume, new program may be created to fix negative stock. With current solution, negative should not be frequent and it will be consolidated at plant level, so initially, exceptions should be handled manually.

• TRANSACTIONS TO BE USWD TO CHECK NEGATIVE STOCK:• MB5L• /AMS/UAMPT01_INV

Variance Calculation

• Counting is be done in the HandHeld and sent to SAP and saved in table /AMS/0UST_AUDI

• From the Audit transaction (/AMS/OUSCS00_AUD_TRX) variance calculation can be triggered

• Process can also be automated by using transaction /AMS/OUSCS01_SBTAUTO by a batch job

• Transaction /AMS/OUSCS01_SBT_VAR can display the variance calculation

• From the same transaction the Shrink Invoice can be triggered or Variance calculation removed/deleted.

Comment: Cycle counts are not received and will not adjust SAP

Counting Done In HH

Sent and saved in SAP

Table with Variance results

Creation of CNA

Documents

Report / adjustments

Job performs consolidation

of docs in SAP

Audit Report

• Transaction /AMS/OUSCS00_AUD_TRX was created for display and change audit information.• Below is a selection criteria for the transaction, and report view

Audit Report

• In the Main Menu Bar, different actions can be performed:

• Audit ID: User can enter an identification to identify the audit, example Q1-2014• Export: Can set the audit to be exported to 3rd parties / EDI. This Export process can also be automated

by transaction /AMS/OUSCS01_SBTAUTO• Mark-Del: Mark the audit for deletion. If marked for deletion the audit is not considered in the variance

research.• Remove Deletion Mark: remove deletion mark of the audit• Variance Research: Trigger Variance research for the audit selected. This process can also be

automated by transaction /AMS/OUSCS01_SBTAUTO• Text: Enter Text in the audit selected. Can be used for example when changing values or for any

relevant comment.• Select: Select/ Mark and Un-mark all displayed lines.

• Secondary Menu Bar can execute different Standard functions like: sort, search, summarize total, subtotals, export to Excel…

Audit Report

• Actions are performed based on the lines that are marked

• Original Audit received can be changed, and this is the value that will be used for the Variance Research. Original information is always kept. It is recommended that when changing the values a comment is inserted in the Text field

Variance Calculation - Report

• Transaction /AMS/OUSCS01_SBT_VAR was created to Display Variance Research, below is an example of the selection criteria.

• Besides different selection criteria, report can display the price based on a Specific Date. • There is also the option to bring just the Variance research for the last audit executed for the

customer

Variance Calculation - Report

• In the Top Menu Bar, different action can be performed:

• Create Shrink Invoice: for the lines selected create the Shrink invoice document• Cancel Shrink Invoice: If the Shrink Invoice was already created it is not possible to create a new

document. For this the original document created need to be cancelled and then this button clicked to allow the new creation of the Shrink Invoice

• Log: For the lines selected inform all the document numbers included in the calculation• Refresh: Refresh the report (example to display the Shrink invoice number after the creation)• Variance Percentage: for the lines marked, performs the Variance Percentage calculation for the lines

selected• Delete Variance Research: delete the variance research marked• Select all: Select/ Mark and un-Mark all the lines displayed

• Report also has standard functionalities for sort, search, filter, totals and subtotals, export, create graphics, create lay out variants..

Variance Calculation - Report• Below there are additional details of some columns available in the report:• Basic Result of the Variance Research

• Total Var% will have the Variance % for the customer. Variance % is per Customer and material group

• SBT Group ID and description and Product Hierarchy level 2 (Pizza or ice Cream)

• Debit and/or Credit memo requests created for the Shrink. $Shk Net will have the total per document number, and $Shk Tot will have the total value for the Shrink considered the credit and debit.

• Same values display at qty level are displayed based on the price (base price)

Variance Calculation – Shrink Lump Sum Adjustment

• From the Variance Report, Shrink Invoice will be created, and by default it will charge the customer by 50%.

• Shrink Document is always created with billing block. So if the % need to be changed, this need to be done before removing the billing block. If there is no change to be done, billing block can be removed.

• Transaction V.23 can be used to remove billing block.

• In case the amount to charge the customer need to adjusted, calculation need to be done outside SAP to find out a % that need to be applied in order to adjust the value of the Shrink Invoice.

• Using transaction VK11 Condition record need to be created for condition ZCCA with the % to be applied, and this value will override the default value – 50% (charge customer 50% of the value)

• Condition can be created in different levels, The recommended sequence is the first one that it is possible to created the entry by Sold-to or customer hierarchy level 1, and can be differentiated by Product hierarchy level 2 (Pizza or Ice cream)

Other Document Flows

SBT Flow - Others


Shrink Invoice

Spoils

Freeze Failure

ZSB2(4) + OrdReason

“SS”+ Condition ZCCA

Invoice Type

ZSB2(4)

ZSB2+ Ord.Reason F1,

F5 or F0 + Condition ZCCB

Invoice Type ZSB2

Acum. Stock

Movement

Acum. Stock

Movement

Order ZSB7+ Ord. Reason

(List)

Delivery Type LR

Movement: 632, returning to SBT logical plant, as blocked and in the Spoil storage location.

Scrapping Cockpit for Bad Goods Movement

(ZS1 or ZS7)

+

F1: Freezer Failure - Charge 100%F5:Freezer Failure - Charge 50%F0: Freezer Failure - Charge 0%

Use ZSB4 when stock is found

Order Created with Billing block

SBT Flow - Others


Stock Adjustment (Manual Exception: move stock from one customer

# to another)

SBT Store Conversion

ZSB2(4) + OrdReason

“OE”+ Condition ZCCA

Invoice Type

ZSB2(4)

ZSB4+ Ord.Reason SN

Invoice Type ZSB2

Acum. Stock

Movement

Acum. Stock

Movement

Total value of order is zero but cost posted to bad goods

SBT Delivery “Cancellation” to

warehouse – Manual Exception

Order ZSB3 + Ord. Reason + Item Cat. ZSB8

- Manual

Delivery Type LR

632: return blocked to the main warehouse

SBT Flow - Others

Type

Shrink

Spoils

Freeze Failure Charge 100%

Document with 100% of the Qty. + ZVSU Cond = 100% Qty to Bad Goods (cost) = 4011010 / VV403- ZCCB Cond = 0% Bad Goods = 4011010 / VV403Base: Price + Discounts / Order Reason:F0

100% Qty to Bad Goods (cost)(when doing the movement for scrapping)Different Order reasons



Other new Order Reasons:SN = SBT Store ConversionSR = SBT Store Leaving



Document with 100% of the Qty. + ZVSU Cond = 100% Qty to Bad Goods (cost) = 4011010 / VV403- ZCCA Cond = 50% Bad Goods = 4011010 / VV403Base: Price / Order Reason: SS

SBT Flow – Freezer Failure

SBT Flow – Spoils

SBT Flow – Shrink

SBT Flow – Example Of Postings – Freezer Failure

Sales order ZSB2 created with Order Reason F5 – Charge 50%

Condition ZCCB is activated to charge customer for 50%

Condition ZVSU is activated to revert Goods Issue and make the posting to Bad Goods


Billing is Created with the Postings as Shown

Stock Movement is created by the consolidation program


Goods Issue is Reverted

Total Cost Is posted to Bad Goods

Charge Customer for 50% and compensate the Bad Goods Account

Accounting in Goods Issue

Accounting in Billing


Account Keys used

SBT SpoilsType Order Type Delivery Type Postings

Spoils

Order ZSB7+ Ord. Reason

(List)

Delivery Type LR

Scrapping Cockpit for Bad Goods Movement

(ZS1 or ZS7)

+

Spoil Document will remove the stock from consignment and return to the SBT logical plant, as blocked and in the Spoil storage location.

Based on the Order reason received in the Spoil Document, Scrapping Cockpit transaction need to be used to make the postings to bad goods to the correct GL account.

For Spoils there is no Physical Return and 100% of the cost is posted to Bad Goods.

Table Below Shows the relationship between the reason code in the Hand Held and the Order reason that will be used in the Spoil document in SAP.

SBT Flow Spoils – Scrapping Cockpit – transaction /GLB/RGTPT00_SCRAP

1) Order ZSB7 created in COM

2) Scrapping Cockpit

3) Display order number and order reason

4) Posting can be done using different Reasons. Select the appropriate reason and the correspondent Movement type will be triggered (affecting different accounts)


• If Order Reason is “CD - Customer – Damage” the Reason DAMAGED AT CUSTOMER should be used and will trigger movement type ZS1 (Scrap Finished Goods due to Damage by customer) need to be used in the Scrapping Cockpit.

• For Recall Reason codes RW and RM – Details in the next page

• For any other Order Reason the Reason EXPIRED DUE TO GD should be used and will trigger the movement type ZS7 (ZS7 - Scrap Finished Goods (BLK) due to customer (other than damage reason)) need to be used in the Scrapping Cockpit. =

5) For Recall – Order Reasons RM and RW

Need to clean the customer field

Then use the Reason as below:

Posting will use movement ZS9 to Bad Goods - Recall


Table Below Shows the relationship between the reason code in the Hand Held and the Order reason that will be used in the Spoil document in SAP.

SBT Flow Spoils – Reason Codes

Movement Reason in Scrap Cockpit ZS1 0001 - CS - DamagedZS1 0002 - Forage - DamagedZS1 0003 - Expiration customerZS1 0004 - Unsold at customerZS7 0001 - Expired FGZS7 0004 - Discontinued FG

In The Scrap Cockpit based on the reasons selected, the below movement types are triggered:

Stock Consolidation Program - /AMS/OUSPT01_SBT

• Scan Data and similar documents (ZSB2, ZSB4, ZSB5 and ZSB6) were configured only as billing relevant, similar to credit and debit memos.

• In order to make the Consignment stock adjustment of what is being consumed by Scan Data and other credit /debit documents, a Program will be executed to select all relevant documents created in a specific period.

• This program will be executed by a batch job, and will have the time depending on the billing job

• The program will create a message (YINVRPT001), that will be replicated to SOS and perform the stock adjustment

Credit/Debit docs

Billing

Credit/Debit docs

Billing

Credit/Debit docs

Billing


group of customers

Stock Adjustment in

SOS


• Transaction /AMS/OUSPT01_SBT was created to consolidate Scan Data Billings (Documents ZSB2, ZSB4, ZSB5 and ZSB6) and create message (YINVRPT001) to SOS to update Consignment Stock. Below is the execution Screen of this transaction that will be executed by a Batch Job.

This should be the Default Parameters for the execution

Regular Batch Job execution will be done based on a specific range of date and time

As Exception, execution can be done by Delta (consolidating all documents created after last execution up to current time minus X minutes. Or based Billing document numbers


Some Recommendations when executing the program:

• Initial time of one day (00:00 hour) should be with the time in blank or the 24:00:00 hours of the previous day, we should avoid execution in the first/last hours of the Day.

• If Execution is done with document created in different days, Idoc will split by creation date of the billing.• Recommendation due to the log table is run with specific time. Delta and by document number should

be exception.• In case a manual execution is done without check the log table for a date in the past or is done by

document, the next execution need to be by specific time. Execution by delta will not work• Document log table is just checked in the execution by document, - so execution by document should be

really an exception and only for documents in the past.• Execution by document, does not save information the execution log, it only saves the information in the

document log table. Execution by document should be done only for documents in the past – considering the last execution in the log table. This could be used in cases that for any reason the document need to be resent. Execution for future documents (based on last execution date/time) , need to be done by Delta or by specific time.

• Idocs are split based on the Document type (ZSB2/ZSB4/ZSB5/ZSB6) and creation date of the billing – Order reason does not create a split.


• Tables below are used to support the process:• /AMS/OUST_CONF: Configuration table to determine documents to be consolidated, movement

type to be used and default batch to be used• /AMS/OUST_EXEC: Table will save the time stamp of the execution of the program and date/time

period that was consolidated in the execution• /AMS/OUST_DOCLOG: will keep the document numbers included in each execution.

• Report /AMS/OUSPT00_STOCK was created for Reconciliation purposes, to match the billings created in COM with the Stock Movement created in SOS.

• Time Stamp (Date and time of the execution) will be the main link for the reconciliation• .In the material Document:

• Document Date: Date that the billing was created• Posting Date: Date that Message was created• Header Text: Will Indicate the Idoc that created the stock movement• Line Text: Time Stamp of the consolidation that can be linked with tables - /AMS/OUST_EXEC and

/AMS/OUST_DOCLOG

Stock Consolidation Report - /AMS/OUSPT00_STOCK

• Tables

Document Flows – Tag (Listing, Price, Credit)

• Listing (item authorization)• Listing will raise a hard error in case material is not listed for the customer. • Listing will be activated for the SBT Delivery (ZSB1), but not for Scan Data and Returns

(ZSB2,ZSB3,ZSB4)• Materials not authorized received in the scan data will need to be checked by a report.

• Price Difference – Issue 42• 3 or 2 Statistical conditions will receive the information of the customer price. Depending on the

customer configuration the appropriate condition will be filled for : Price, Promotion, Net Price.• Net is needed or only price and promo (net=price, and differences by report)

• A statistical condition will calculate the difference between customer and system price • SBT will post using System Price, and differences will handled in AR• Differences / discrepancies will need to be checked in a BW report

• Credit• SBT delivery: not relevant for credit and not part of the credit exposure..• Scan data: Will not be relevant for credit, but documents will be part of the credit exposure.• Blocks need to be done at the customer master level to avoid document creation

Master Data

Master Data – SBT Group

• Customer Group 3 (KNVV – KVGR3), will represent the SBT Group. It is also used to group Headquarters. For SBT it should start with S**.

• SBT Group will be used:• Create item authorizations (listings)• Keep Consignment Stock position in SAP – For Each SBT Group one customer # need to be defined to

be used to keep consignment stock• Define materials to split Scan Data for shared UPC• Define materials to split in the creation of the Shrink invoice (from Material group to material)• Identify if customer is SBT for Ice Cream and Pizza (based on product Hierarchy level 2). This

information will sent to Handheld to define the order type to be created.• Define high level rules for EDI messages (send to PCG/Icontrol/Customer)

• Recommendation is to have groups with customers with the same item authorizations. Exceptions can be created, but the result will be:

• Handheld will be able to allow just the correct materials for each customer. HH will receive all Listings, exclusions and exceptions rules

• When receiving scan data of shared UPC, the split will use materials with the same UPC that was delivered for the group, it may result that in the Scan Data is used a material that is not listed for the specific customer, but is authorized for the Group.

• Similar to the above can happen for the Shrink Invoice creation.

• If Inside the group we start to have many exceptions, recommendation is to Split the groups. Need to really create groups of customers with same characteristics to avoid exceptions, and less effort to control.


• When Creating a new Customer or new group, the steps below need to be followed.1. Define the group that the customer will be included2. If it is a new group, ask the configuration of the new value for the customer group 33. Confirm in the customer master (production) if the customer has the correct value for the customer

group 3, if not request the customer to be updated.4. Use transaction /AMS/OUSCS00_SBT

• If it is a new SBT group, create the SBT group in the transaction and include the additional information needed (contact, phone, receive time)

• The most important step for a new SBT Group, is to define the customer number (one customer that is in the group) that will represent the group for the consignment stock. Recommendation is to define the

• If it is a new customer in a existing group enter the customer in the group and include the start and end date of the customer.

• In order to Include the customer in the group the Customer Group 3 field of the customer need to be with the correct information.

5. Confirm Listings, Inform other teams like EDI, MH, Inventory Control as needed

IMPORTANT: For each Group there is one customer # that will be used to keep the consignment stock in SAP. This number should be changed once we already have transactions. If for any situation we need to change the Customer or merge/split groups, CS and MH need to work together to make the proper stock adjustments from one customer # to another.


• Transaction /AMS/OUSCS00_SBT

This is the initial selection Screen. Sales Area for SBT will always be US06 07 00. SBT can be selected or not in the initial Screen.

Once you enter in the transaction, in the button Menu, different actions can be performed, depending on the line that is selected.


When one line in the Header is selected and then selected in the menu View details, the customers assigned to the group and the Product Hierarchy level 2 under SBT are shown in the bottom. Customer can only be inserted in a group if the Customer Group 3 is correctly maintained in the customer master.

Field Invoice Rule: Enter “1” if when creating the Shrink Invoice the Document is created with a billing block


New SBT Customer

Need new

Group?

Define Group

Configuration of the new group (create value in

SAP)

Update customer master

Update SBT master data Trx (set the group)

Inform EDI Team for

necessary changes

Update Listings

Is Cust. Master

Correct?

Update Customer in

SAP

Enter Customer in the SBT

master Data Trx

Enter Start and End date and additional info

No

Yes

Yes

No


Change the consignment stock from one customer number to another

• Create a ZSB2 Document with Order reason OE for the customer that want to remove the Stock

• Change the customer master to the new customer

• Create a ZSB4 Document with Order reason OE for the customer that want to put the Stock in consignment

• Bad Goods account will be used for the postings. If same materials and Qtys are used in ZSB2 and ZSB4, the net of the transaction in the bad goods account will be zero.

Store conversion in and out SBT

Store conversion

• Convert Store in SBT, with existing inventory• Inventory need to be counted by material, using generic batch• Count need to be done before the start day of the first scan data (before store open or previous day

with store closed)• Based on this count, document ZSB4 will be created in SAP with a specific reason code, and detailed

by material. This information will be sent as the first Delivery to the customer, and initial count created as zero.

• Prepare master data: • Define SBT group for the customer (SBT type – pizza/ice; outbound messages)• Include Customer in the SBT group (Customer master update)• Enter start and end date of the customer• Maintain listing and material authorization by SBT group and remove any other rule (sold-to)• Review pending documents and plan the counting based on date that there is no open

document, or document with wrong order type being created. Make proper adjustments.• Manually enter a zero audit to identify the start for the first variance research. Does not need to

load zero for all the classes, just one would be enough. This audit need to have the report Date as 1 day before the billing date of the SBT Conversion document (Billing date of the document), received from HH.

• Based on the start date of the customer and delivery date, SBT document types (ZSB1 – SBT delivery) need to be used.

• If store is fulfilled by warehouse, need to set a procedure with the customer to stop to send materials from warehouse to store, and delivery will be done NDSD.

• Review possible impacts in pricing (warehouse x NDSD) and probably create an adjustment document if necessary (ZDR), as NDSD price may be higher than warehouse.

Store conversion

• New store in SBT of existing chain• Prepare master data:

• Customer number created and prepared • Define SBT group for the customer• Include Customer in the SBT group (customer master update or during creation)• Enter start and end date of the customer• Manually enter a zero audit to identify the start for the first variance research.• Review listing and material authorization by SBT group and remove any other rule (sold-to)• Initial balance for the store will be zero• Start to receive Scan data and SBT delivery information

• New material or new division in an existing store: • Similar to the process above, preparing material master data for the material:

• Review listing and material authorization by SBT group and remove any other rule (sold-to)

Store conversion

• Store leaving SBT• Update end date of the customer, as the last day that the Scan data should be received.• EDI should not accept Scan data of this customer after this date, should manually maintain customer

table, removing customer, once scan data of the period was received.• Perform the count in the following morning of last scan data (material level) Based on the count,

create document ZSB2, simulating a sale (scan data) of all the remaining materials at the store Once this document created and all scan data of the period is processed, consider the last count as zero and perform the last variance research, charging the customer according to the preference (together with other store or separate)

• Similar process applies for the complete Chain (store by store) or just one material or group of materials leaving SBT.

• Another alternative is to only enter a final audit as zero, trigger the variance research and create the Shrink invoice. It can be decide if the debit will be created as a Shrink or as a regular billing (full price). The only change that need to be done would be in the Order Reason of the Shrink document, to put as blank and reprice the document to get full price.

For the scenarios that one specific location is closing , but the chain still in SBT:• Buyback closed/full boxes• Destroy open units

• Option 1: Spoils process – no charges to the customers• Option 2: Shrink Document – Charge the customer (enter zero audit for variance research)

EDI

• Scan Data: Received in SAP creating documents ZSB2 or ZSB4. Message Type: ORDERS = > IDOC: ORDER05 => Extension: /GLB/OGTORDERS05_02

• Source of all interfaces below: SAP x HAL• Price• Promo• Material• SBT Deliveries• Audit Count

• EDI processing tool for SBT Scan Data

Reports

SBT Reports

• List of deliveries and invoices: OTR and BW

• Materials authorized but not sold: BW (BW + Excel)

• Discontinued/ not authorized materials that were sold: BW (BW + Excel)

• Large quantity order lines: BW

• Zero volume report: BW

• Rejects: OTR / BW

• KPI reason code for rejects: BW

• Price Differences: BW

• Late Scan Report: New Report in SAP

• Delivery to Scan report: NUSA BW.

Developments and Technical Details

SBT Master Data: DEVWR0030392

Description: SBT customers are grouped in SBT groups, this transaction is used to define the groups and also provide additional information needed for the SBT process:

• Define the SBT Groups (based on the customer group 3 field – KNVV-KVGR3)• Define the customer number that will be used to keep the stock in consignment• Define customers in each group• Define product Hierarchy (pizza/ice cream) for each group• Define start and end date of each customer for SBT• Define contact information for customer (displayed in late scan report)

Information is interfaced to Visicom/Handheld, so HH what are the dates that the customer is active for SBT and this will be used to define the order type that will be created for the customer (ZSB1- if SBT / OR – Non SBT).

Initially HH would also define the Order type based on the Product hierarchy, but this functionality was not created in Visicom and also the Business does not have any scenario that the customer is SBT for one category, but not for other (pizza x icecream)

IMPORTANT: Definition of the customer that represents the SBT group can not be changed without analysis. This information is used to keep the stock in consignment. If there is a need to change the customer, the balance of the stock in consignment also need to be changed for the new customer.

SBT Master Data: DEVWR0030392

Main Transaction: /AMS/OUSCS00_SBT

Tables:• /AMS/OUST_CUSGP: Customer Group• /AMS/OUST_CUSTB: Customers associated to the group• /AMS/OUST_MATGP: Prod Hierarchy 2 associated to the group

Transactions for direct access in the table:• /AMS/OUSCS00_CUSGP: Access to Customer Group table /AMS/OUST_CUSGP• /AMS/OUSCS00_CUSTB: Access to Customers associated to the group table /AMS/OUST_CUSTB• /AMS/OUSCS00_MATGP: Access to Prod Hierarchy 2 associated to the group – table

/AMS/OUST_MATGP

SBT Variance Research, Audit, Split and Shrink creation: DEVWR0030391

Description:This development was created for different functionalities/transactions there are part of the audit and variance process: Variance research report and calculation, keep and edit audit information, process for Shrink document creation, process/table to keep % to split the shrink at the mat.grp1 level into material, and others.

Main developments created:

DEVWR0030391: US_NUSA_0939_CS_SBT_Variance CalculationDEVWR0030479: US_NUSA_0939_CS_SBT Audit and % tableDEVWR0030480: US_NUSA_0939_CS_SBT Shrink Invoice Creation

COMMENT: initially it was created as just one development, as they are very related, but due to the complexity of the programs and also to try to anticipate some of the developments, it was split in 3. DEVWR0030391 was kept as the main one, so all DEVCRs needed were raised based on this development, that contains all the details.


Audit Transactions:• /AMS/OUSCS00_AUD_TRX: Audit USER Transaction• /AMS/0USCS00_AUDI: Transaction for direct access to table /AMS/0UST_AUDI

Audit Table:• /AMS/0UST_AUDI: Audit table - this table will receive the audit/count information from the handheld and

will use in the variance research calculation

Split Transactions / Tables• /AMS/OUSCS01_SPLIT: transaction that executes program /AMS/OUSCSR_SBT_SPLIT_PROGM to

calculate the %s of the stock by SBT group/EAN/MVGR1. This transaction will be executed by job, to update the % (after billing and consolidation programs).

• /AMS/0USCS00_SPLI: Transaction to access table /AMS/0UST_SPLI

Split Table:• /AMS/0UST_SPLI: Split% Table: this table will keep the stock % to be split by material group and UPC. It

will be used for limited edition split (by UPC) and also to split the variance calculated by material group (by mat.grp1)


Variance Research Transactions• /AMS/OUSCS01_SBT_VAR: USER Report for the variance research• /AMS/OUSCS01_SBTVAR2: Variant of transaction /AMS/OUSCS01_SBT_VAR without the trigger of

shrink and deletion of variance calculation.

• /AMS/OUSCS01_SBTAUTO: This is not an user transaction, it executes the program /AMS/OUSCSR_SBT_AUTO_VAR_PRGM for the automation of the variance research. Will be used as a batch job, depending on the market definition.

• /AMS/OUSCS00_VAR_PRG: This is not an user transaction, it executes the program /AMS/OUSCSR_SBT_VARIANCE_PRGM, that is executed inside the report to run the variance research consolidation/calculation.

• /AMS/OUSCS01_VAR_AUD: Load history and audit tables. To be used in the conversion of variance research history from legacy, but can also be used to load audit from an excel.

• /AMS/0USCS00_VAR_R: Access to table /AMS/0UST_VAR_R – Variance Research Calculation• /AMS/0USCS00_VARC: Access to table /AMS/0UST_VARC – Variance Research Configuration• /AMS/0USCS00_VARL: Access to table /AMS/0UST_VARL - Variance Research Log


Variance Research Tables:• /AMS/0UST_VAR_H:Variance research history table - history data to be included in the calculation of the

variance research – to be used during cutover and transitions from legacy to Globe.• /AMS/0UST_VAR_R: Variance Research table: Store the calculation done for the variance research,

based on the audit information and documents created in SAP• /AMS/0UST_VARC: Variance research configuration table: this table store the documents to be selected

by the program and how it should be used in the variance research calculation• /AMS/0UST_VARL: Variance Research Log: keep the document numbers included in the variance

research calculation

Others:• FM /AMS/UUS_STOCK_SOS: This part was included in the original scope of the variance research report

but there will be no scenario that we will only have a material document created. Originally this would be for Spoil process, but then the design was changed to have a sales document for this process. SOS extraction to get stock movements

• JOB_SUBMIT_PROG: When variance research is triggered this job: JOB_SUBMIT_PROG is triggered. So status/performance of the execution can the followed by looking sm37 for this job.

• Class (se24) /AMS/CL_OUSCS_SBT_VARIAN_TRX method CALCULATE_MATR_QUANT – Methid that is used to split the material group information in material level for the Shrink Invoice

Scan Data Consolidated Stock Movement: DEVWR0030526

Scan Data Consolidation Transactions:• /AMS/OUSPT01_SBT – Program /AMS/OUSPTR_CONSOL_STOCK_MOVE - transaction create to

execute the stock consolidation. This program will be executed by a batch job. Some comments:1) Initial time of one day should be with the time in blank or the 24:00:00 hours of the previous day2) Recommendation due to the log table is run with specific time, not by delta, delta should be exception.3) In case a manual execution is done without check the log table for a date in the past, the next execution need to be by specific time. Execution by delta will not work.

• /AMS/OUSPT00_STOCK: Report for stock consolidation. Compares the billing created in a period or included in one execution with the stock adjustments done in SOS.

Scan Data Consolidation Tables:• /AMS/OUST_CONF: SBT Stock Movement configuration table• /AMS/OUST_EXEC: SBT Stock Movement Execution table• /AMS/OUST_DOCLOG: SBT Stock Movement Document log table

Others• /AMS/CL_OUSPT_SBT_STOCKMOVEMNTCP Class• get_documents Method to select the documents•• /NESGLB/MINVRPT table to configure message: YINVRPT001•• Idoc Seg: /NESGLB/E1MBXYI_01• Extension YWMMBID1

SBT Delivery Consolidated Stock Movement: DEVWR0030528

• Table /AMS/OUST_CONFI configuration table•• S_LE_SHP_GM_06 /AMS/OUS_POP_MATERIAL_SBT : Used for doing PGI for creation of

Material document. Activate for Plant in NUSA - US08• S_MV45AFZZ_82 /AMS/OUS_SBT_PARTNER_DETERMINE : Used to create sales order for SB

partner function. Activated for US06 - sales org

Default values in the Order: DEVWR0032529

• /AMS/OUSCS01_DEF /AMS/0UST_DEFAL "Functions in User exit table:/AMS/OUS_BUYBACK_SALES_ORD/AMS/OUS_BUYBACK_SALES_ORD1"

Late Scan Report: DEVWR0030423

• /AMS/OUSCS00_SBT_SCN /AMS/OUSCSR_SBT_LATE_SCAN_REPT Late Scan Report

SBT Master Data to Visicom: DEVWR0030975

• DEVWR0030976 – Visicom part

• Program /AMS/OUSCSO_SBT_SAP_VISICOM• Partner: USEDDHH001• Idoc type: /GLB/RGT_CUSTOM_TAB_OUTBOUND• Message type: /GLB/RGTTAB_MULTIPLE_TABLES• F:/zdata/AR/HAM/US/in/USEDDHH001/csotable01

SBT Audit to Visicom: DEVWR0030694

• DEVWR0030977 – Visicom part

• F:/zdata/AR/HAM/US/out/csiaudit01 SAP: /zdata/<SYSID>/us/glb/usesbtaudi/pdisbtaudi/ /GLB/RGTFC_CACS_FILE_COPY = Load file in ZDATA

• program /AMS/OAMPDI_SBT_AUDITINFO •• § XI will get the file in a shared folder• § XI will save the file in the ZDATA folder (will rename and use a timestamp)

• § XI will create an inbound IDOC in COM with the message type /GLB/XGT_FILE_TO_IDOC and partner USESBTAUDI

• · In the segments of the IDOC we will have only the file name saved in ZDATA that should be something like

• · US16.USESBTAUDI.PDISBTAUDI.ddmmyyyyhhmmss.CSV• § SAP will trigger the execution of this IDOC, a GLB function will be called and it will

• · Read the configuration of the table /NESGLB/XEINTID based on file name in the segment, in this case US16 USESBTAUDI PDISBTAUDI

• · In this table we have the name of the program that actually will read the file /AMS/OAMPDI_SBT_AUDITINFO and also the variant US_9999_D_0001 and the ZDATA path

• · The GLB function will change the variant replacing the new file name and then will trigger the execution of this AMS program

• · (Note: These steps above are common for all Dummy IDOC solutions, is the configuration in the /NESGLB/XEINTID that defines which program will be executed in the end)

• § The program /AMS/OAMPDI_SBT_AUDITINFO will read the file informed in the ZDATA path, do the validation and update the custom table

SBT EDI

• /AMS/OUST_DUN Control table: EDI partner• /AMS/OUST_OCTRL Control table:• /AMS/OUST_UOM Control table:••• /AMS/OAMT_SBTOUTPrice, promo, product:controla qual informacao deve enviar• /AMS/OAMT_SBTITM Price, promo, product: Item / product table - 888• /AMS/OAMT_SBTPRO Price, promo, product: Promo table - 889• /AMS/OAMT_SBTPRCPrice, promo, product: Price table - 879• /AMS/OAMCS_SBT_EXTR Price, promo, product: This is for updating custom table

/AMS/OAMT_SBTITM. /AMS/OAMT_SBTPRC, /AMS/OAMT_SBTPRO• /AMS/OAMCS_SBT_IDOC Price, promo, product:Create file and transmits to XI then to

market end point•• /AMS/OUSCS00_SBT_ADT send audit information - 852• /AMS/OUSCS01_SBT_DEL send delivery information - 810•• EDI - Inbound scan data• /AMS/OUS_EDI_SBT_SCANDATA Exit for material determination

Back up Slides

Negative Stocks

• There is no mention about negative stock in NAS because this is a not possible event (meaning that is an event that should not happen).

• It will be difficult to explain to an auditor negative stocks in a PEC close or in a year-end closing (this is not the direction to go as system design point of view).

• Ensure that at PEC time the situation is aligned and that there is no negative stock in the plant.

• With the explanation of the process, we understand that negative stock in the plant is quite unlikely to happen.

• In the event that there is negative stock at period end, there is no time for a manual correction. A correction program needs to be sketched up.

• We need to decide the level on which the stock is corrected (so that there is no negative inventory). FI requires the dimension Material/Plant. If required by Customer Service the dimension could be Material/Plant/Customer(shop).

• Adjustment program will increase inventory with posting to bad goods and decrease inventory of another material in the class. Rule for this needs to agreed by the business.

• The setting proposed is only applicable to Dreyers and Pizza (US16 plants) and no other market is allowed to have this setting

Negative Stocks

We should never have negative stock at the plant level (Total plant/material):• COGS bolt on will have technical problems if there is negative stock. Application is not prepared for this. • There is a number of developments in Material Ledger that would need to be reviewed if we have negative

stock in the plant.

Example above created in RC7

Pricing IA: Tag Process Variance

Apr 21, 202382

As-Is: • Tag variance could be promotion or price variance.

To be:• Condition type and 3006200 GL account and VV152 yet to be determined.

Open Issue:• There could be 3 variances – promotion, price, & net price; or only one

variance, it is yet to be determined. (Issue 42, due 2/15)• If should accept HH price for DD and system price for SBT is yet to be

decided. (Issue 42, due 2/15)• Proposed 3006200 GL account and VV152 are yet to be agreed by GAR.• Condition type is yet to be determined pending on GL determination.• May need a development routine to calculate variance.

High Level Design

SAP

COM SOS

Hand Held Backoffice

Variance Research

SBT Delivery Freezer Failures

SpoilsAudit

Cycle Count

CNA Invoice

Split Criteria

%EDI

Scan DataAudit Table

SBT Delivery

DeliveryFile from

HHIDOC

• Movement type to consolidate consignment stock in the unique plant by customer group

Order

• Listings Activated• Pricing activated• No credit check

SBT Scan Data

Material Movement

BillingFile IDOC

• EDI maps• Customer and sales area

determination• Material Conversion• Customer Invoice Number• Split Debits and Credits• Customer Price• SBT Ice Cream and Pizza split• Dreyers of Las Vegas• Processing Reports

Credit/ Debit Memo

• Material determination• Limited Edition Split Logic • Document flow• No inclusions (listing)• Price procedure

• Consolidation program for inventory movement

• Batch Determination• Negative stock process in

PEC

SBT Audit

CNA Invoice

Performs Count in

HH

Receive in SAP

• Edit Audit• Trigger variance Research calculation• Send count to 3rd parties

Variance Table in

SAP

• Program to calculate totals for variance• Report to display/ select data from variance

table• Consolidation / Filters/EDI Group• Trigger Creation of the CNA Invoice

• Configuration for document flow• Process for lumpsum

adjustment• Pricing

• Generate file with counting

Material Movement • Consolidation for daily stock adjustment

• Posting to bad goods

SBT Globe Solution

Documents

Transcript of SBT Globe Solution