Sunday, 1 July 2018

Topic - 11_Automotive Template - SAP Model

Organisational Structure :--
Company Code: - 9800, 675W, 586W
Sales Org :- 9800, 675W,586W, 47BW, 900W, 49AW,904W, 9160
Distribution Channel :-- E0
Division :-- 01
Pricing Procedure :- Y00001
Delivering plant :-- 398W,675W,586W,47BW,900W,49AW,398W,9160
Business Area : -- 2050

Different Sales Document Type used in the Automotive Template : --

YG46 (Credit Memo request), YG42 (Credit Memo request),YARZ (Returns Cust Order), YATA (Standard Order), YAPL
(Scheduling Agreement), YG31 (Credit Memo request), YG32 (Credit Memo request)...YL32 (Debit memo request)

Item Category Type : -- YG2N, YARE (Return), YATA (Standard), YAPY(Scheduling), YG2W (Credit memo request),
YL2W (Debit memo request)

Schedule Category Type : -- CP/CN, YR(Return), CP/CN (Standard), L1/CN(Scheduling), CP/CN,LB

Business Entities :- Chasis Control ; AE ; Diesel System; AA; Gasoline System ; CM

Business Process at UBK RM:

1: OE Sales (Toyota, )
2: OES Sales (Spare Parts) this is also regarded as Triangulation case
3: Stock Transfer between Bosch Plant (Intra and inter)
4: Dien Sales
5: Wlag Sales

6: EDL Plant
 System Architecture: -

Horizontal server is POE

Vertical server are AE, CC,DS, AA… and these are all linked to POE selling server.

LOE --- > XOE, YOE, ZOE --- > QOE --- > POE
L99 ---- > X99, Y99, Z99 --- > Q99 --- > P99

Type of Customers in the Template -

Internal Account Group – RB91

External Account Group – RB90

 Material: --

Types of Material in UBK RM –

1: Direct (Serial Production Material and Sample)
2: Indirect (Tooling)

Sales Order Management: --

This consists of three sub-segments as:

1- Inbound EDI Management,
2 – Schedule and Order maintenance,
3 – Customer Logistics Planning

The responsibility of Customer Logistics Planning: -- Response to Customer Query for mapping
address, Get information on S sales Order and Delivery Status, Reconciliation of special activity such as
special freight and alt packing, Creation and maintenance of Customer Contacts,
Management Crisis management situation like containment actions…

Production: -- Three major sub section are entitled here Production planning, Production, Production
Packaging labeling. Here there are two different interface which acts upon…one is DRI (Demand
Replication Interface) this transfer requirements to GB system and once the stock
details are updated, Plant delivery interface initiates further process at Warehouse
management.

Shipping Process: -- Shipping Preparation, Shipping Execution, Shipping post processing

(Notification to Customer)

Outbound Value stream Process: --

Invoicing – This is done by Bosch based on the Goods and services consumed by Bosch’s
Customer and this can be either manual or Automatic.

A/R – Here the financial relationship with the Customer is managed and the payments are tracked.

Self Billing – Customer creates an invoice on behalf of Bosch, based on quantities received and
Purchasing price master. Based on shipping quantities and sales price master, Bosch creates internal
invoices to
Post in financial accounting and accounts receivable. Bosch compares self billing data, such as the
delivery note number with internal invoices and adds self billing number to accounts receivable.
Differences are monitored and clarified with the sales and logistics department.

Cash Management – Customer triggers customer bank about payment to Bosch. Customer bank transfers
money to Bosch bank by wire. Bosch bank notifies Bosch about the money receipt. Bosch posts
payment in financial accounting and accounts receivable.

Dispute Management -- Dispute Management handles the differences between customer payment and
Bosch
invoice.
􀀗 Main steps in Dispute Management are:
- Identifying the reasons for discrepancies
- Handling clarifications
- Agreeing upon a resolution
- Taking actions or following up

Master Data of UBK RM: ---

Type of Master data set is – Customer, Material, Info record, Price, Output

Customer Master Data is stored in Productive system for Master Data (PMD) servers. PMD is the name
of the server where the Customer Master Data is maintained for different systems .This also includes the
migration of Master Data using XML format.

Details which is maintained at Customer Master Record: --

General Data (Address, Marketing, Export, Control Data)
Sales Area Data (Sales, Shipping, Billing document, Partner function)

Company Code Data

Material Master Record: --

Case A: Finished Goods FERT

The finished goods material master provides the following details:

Material Type
Material Group
Procurement Type
Valuation Class
Price Control
Sales GB (An organizational unit responsible for processing sales of certain products or
services)

The finished goods and trading goods materials have a 13-digit number.

Non-stock materials are:

- A byproduct of other main materials that is produced.
- Quality Check failed materials that are returned by the customer.

- Quality check failed materials after production.

Packing Materials (Item Cat Grp VERP):

The material created for packing purposes is called packing material in

which the main material will be packed.
In UBK-RM, Packaging Material has flown from the PaGOS system to SAP.
PaGOS system is a centrally controlled system for creating packaging material (ten digits), packaging
instruction, and Packaging Proposal.

Packing Instructions consist of the following information:

Materials that are packed.
Quantity
Method of packing
Packaging materials used
Packing Instructions (POP3)
As per UBK-RM standards, packaging material, Bill Of Material (BOM) and instruction has to flow from the
PaGOS system.

Using Customer Material Information Record, returnable and non-returnable packaging material can be
differentiated for the customer.

Pricing: --

PHEK Price transaction enables viewing the Standard Cost Price of the material. If the Trading Partner
field of the customer master record and legal entity is the same, the system automatically picks the
condition type YPHK. The condition type YPHK (Standard cost condition type) reads the price from the
material master (Accounting View
1) from the field Standard Price. There is no need for maintaining any pricing conditions for this condition
type.
Surcharge Condition: --
Surcharge refers to levy amount/charges added to the Standard Price using Condition Type YZKU in the
External Customer’s Bill amount. This is manually added at the Sales Order level.

Transfer Price: --
A Transfer Price needs to be created for transferring products between the Business Units belonging to
the same group.
YTP0 will be fetched if and only if the Customer Trading Partner Number and Legal Entity’s Trading
Partner Number are not similar. This value is fetched from Condition record.

Special Partners to Ship to Relationship

Displaying Pool Point Partner (MK03) –

Pool Point is a freight consolidation point that is specified by a customer, Electronic Data Interchange
(EDI) customers assign a location to the Pool Point and that location is required in the Advanced Shipping
Notification (ASN). Pool Point is referred to as a Forwarding Agent.
This is of Vendor Account Group RB98

/n/rb04/yp3_uspc (T-code) --- > During the creation of the shipment documents, the partner details are
maintained
by default. The determined partner roles will be copied into the assigned deliveries, so that they are
available for the Advanced Shipping Notification (ASN) on delivery level.

Displaying Forwarding Agent (MK03) --- > Vendor Account Group: RB15
/n/rb04/yp3_uspc (T-code) --- > The Forwarding Agent has to be defined in this t-code.

Displaying Standard Carrier Alpha Code Master: --

Standard Carrier Alpha Code (SCAC) is a unique code used to identify transportation companies. Within
SAP, a carrier is referred to as a Forwarding Agent. Bosch classifies carriers into ‘Brokers’ and ‘Pick-Up
Carriers’
Brokers: Routed carriers of record as per the customer’s routing instructions.
Pick-up Carriers: Carriers which are actually picking up the material when the carrier of record
is unable to do so.
In some cases, a carrier may have multiple SCAC codes in the system depending upon the customer
to whom they are delivering.
Same Account group as above and details have to be set in the Custom t-code…

Displaying Intermediate Consignee:

Intermediate Consignee processes the shipment and delivers it to the customer location. The customer is
assigned to the IC for the details to appear in ASN (Advanced Shipping Notification). Advanced Shipping
Notification (ASN) is a document that provides detailed information about a pending delivery and notifies
customers about the quantity to be delivered and the actual arrival date at the customer’s point.

Account Group – same as above and the same kind of t-code setting has to be done.

Output Master
Displaying Delivery Output Master (VV23)
The output type used for this business case is YLAV

Displaying Handling Unit Output Master(VV63)

The various output types, that can be maintained for the handling units, are:
> YA02 (Master Label)
> YAHS (HU-from for confirm)
> Output types Z001 till Z142 (RBNA specific-output types)
> YA01 (Sub label)
The t-code “/n/rb04/yp3_tnadu”, Default printer details are to be maintained for the relevant HU outputs
in the TNADU table. TNADU table is a customized table required for maintaining default printers in SAP.
This is required for automatic printing of documents.

Display Shipment Output Master (VV73):

Following is the list of available Shipment Output Types:
YMBL- MasterBOL USA
YLAU - Cargolist USA Letter
YF8G - GTS invoice

Display an Invoice Output Master (VV33):

The various output types that can be maintained for invoices are:
YD50 – Original invoice print out hard copy
YD51 – Duplicate copy of the invoice
YD52 – Archive copy of the invoice
YD56 – Invoice via e-mail
YINB – Invoice via EDI

Details of Custom tables: --

Display Customizing Table: /RB04/YP3_KUPM

The Customizing table /RB04/YP3_KUPM controls the Packaging Material information. Customizing
Table RB04/YP3_KUPM can be viewed in the following:
- Handling Unit label
- Shipment Documents
- Print/EDI outputs related to delivery

Display the Customizing Table: /RB04/YP3_PRMEDI (/N/RB04/YP3_PRMEDI)

The customizing table /RB04/YP3_PRMEDI controls many functions for Shipment processing. Below details are updated in the custom
table…

Advanced shipping notice (ASN) is a document that provides detailed information about a pending
delivery. The purpose of an ASN is to notify the customer when shipping occurs and provide physical
characteristics about the shipment so the customer can be prepared to accept delivery.

Introduction to Sales Order Management :


􀀗Sales Order Management manages the customers sales orders and scheduling agreements.
􀀗Sales orders and scheduling agreements are prepared based on the types of sales
activities:
- Delivery of goods
- Delivery of services
Type of Sales Scenario -

Inbound EDI Management: From Gentran to EDI Manager

Inbound EDI Management: From EDI Manager to GLORIA

Schedule Maintenance

The three types of scheduling agreements are Standard, JIT, and RAN Scheduling Agreement.
The Customer Logistics Planner in Bosch creates scheduling agreements manually in GLORIA with
inputs from master Data. Price and tax determination happen in the background when scheduling
agreements or sales orders are created.

Scheduling agreements are updated with delivery schedule information based on data from IDocs.
After the scheduling agreements are determined, they are updated with the delivery schedule and
delivery quantity.

Steps to Create Due Delivery Schedules

Customer Logistics Planning
Scheduling Agreement:
A Scheduling Agreement is a controlling document consisting of
details of predefined delivery dates and quantities to be delivered to the customer as per the
Agreement between a Business Organization and the Customer. Customer can pre-schedule deliveries
by sending the releases via EDI. An ‘830’ Weekly Release and an ‘862’ Daily Ship Schedules sent via
EDI are automatically loaded in the SAP system and assigned to the appropriate Scheduling Agreement.

Net Value is displayed Condition Type – YNP0 (Net Price) is used in case of Sales Document involving
external customers.
Supplier Code, MRP Type, unloading point, Text-shipping instruction has to be noted at SA level…
For a Scheduling Agreement type YAPL ‘D', requirements according to validity or deliveries according to JIT is determined automatically. If a
customer only transmits forecast information for the delivery, it needs to be changed manually to ‘B' which is requirements and deliveries
according to validity. For a Scheduling Agreement type YAPJ ‘B', requirements and deliveries according to validity are determined
automatically. For a Scheduling Agreement type YAPP ‘C', requirements according to Forecast Delivery Schedule or deliveries according to
JIT are determined automatically.

Customer Return Order (YARZ)

Following are the reasons for Creating Customer Return Order:

Defective material
Over delivery
Wrong delivery
Goods damaged in transit

Order Reason

Credit memo request (yg31), Debit memo request (yl31): This is created with reference to billing
document, Order reason, Reason for Rejection…

Production: --

Posting Finished Goods in Vertical System/Horizontal system: -- > Movement type 131 is used for posting
the finished goods from production to the stock. Movement type 917 is used for posting the finished
goods stock from the vertical system into the horizontal system.

Movement type 915 is used for posting the finished goods stock from the vertical system into the
horizontal system. Movement type 915 generates the Material document while posting the finished goods
into stock. Using the Posting Finished Goods in Horizontal System transaction, the following
properties of a Material document can be viewed:
Material Number
Batch
Storage Location
Accounting Document

Warehouse Management: --

Display Warehouse Activity Monitor (/RB04/YL2_LAGER_MAST)

Warehouse Activity Monitor provides the following information:
- Material Stock
- Warehouse
- Plant Details of the Material
Creating Transfer Order from Delivery Note: -- Transfer Order from Delivery Note (LT03) and Cancel a
Transfer Order for a Storage Unit (LT16)

Selecting a Handling Unit for Posting /RB04/YL2_HUMO: In a business, the Handling Unit could be blocked for reasons such as invoice
discrepancy or quality issues.

Create Transfer Order for Storage Unit (LT09): A Transfer Order for a Storage Unit is created by entering
the quantity that needs to be transferred. A Storage Unit is a logical grouping of material quantities that
can be managed within a warehouse as a cohesive unit.
The transfer order created is confirmed using the transaction code LT12.

Shipping Process:-

Creating Delivery via VL10E (STANDARD DELIVERY)

Creating Delivery via JITK (KANBAN DELIVERY)

Change Delivery (ZACS_ASNMON):

During Change Delivery process, the following tasks can be performed:
Changing Delivery Quantity
Packing and re-packing of the material
Creating Transfer Order

Text maintenance at Delivery level: -

YBOL – USA Bill of lading
YDLP – USA Schedule picklist
YKFG – RB delivery Note
YPKL – USA Packing List

Zshpmon: - This t-code is used for Shipping monitor.

Create Transfer Order (ZSHPMON): -- The t-code can be used for generating TO for the outbound
delivery
Print Delivery Pick List (ZSHPMON): -- A Transfer Order should be created and confirmed before printing
the pick list document.
Confirm Transfer Order (ZSHPMON): -- In event of confirming TO, you need to Pack i.e Assign HU to TO
through Packing material.
Create Delivery document for Non-Stock Materials(VA02): -- Text details, Foreign trade/Custom

Invoicing: --

The standard billing types (UBK RM):

YF21: Billing type for non-Bosch customers
YF25: Billing type for free of charge
YF61: Billing type for affiliate customers
YF91: Billing type for sale within same legal entity

Invoice Print Output – Content:

The output type YD50 denotes Original Invoice Hardcopy.

The output type YD51 denotes Duplicate Copy of Invoice Print.
The output type YD56 denotes Invoice output in e-mail format.
The output type YINB denotes Invoice EDI output.

Printing Credit Memo:

YD31 output type is used for generating the output for credit memo.
Accounts Receivable:
Accounts Receivable process:
Manages the financial relationship with a customer.
Begins when an invoice is generated for products or services delivered to the customer.
Perform effective Credit Control
Analyze receivable forecast per customer group
Analyze revenue turnover per customer group
Evaluate Open Items based on customer groups within or across legal entities
Calculate provision for doubtful debts

Classification of receivables are:

􀀗Receivables from third party companies
􀀗Receivables from quota-consolidated companies
􀀗Receivables from affiliated companies which are not consolidated
􀀗Receivables from investments
􀀗Receivables from consolidated companies

Maintaining Partner Profile for a Customer: Partner Profile for a Customer (WE20)
Maintaining the Partner Profile for a Customer involves the following steps:
- The customer sends a file (820) with self billing data for the deliveries.
- This file is processed through GenTran, and transformed into an
IDoc.
Partner profile is maintained with the message type "REMADV".

Display Customer Remittance Advice (/n/rb04/yci_ca_820):

A Customer Remittance Advice is a letter sent by a customer to a supplier, to inform the supplier that their
invoice has been paid. In a cash application process, customers send a file (820) with Self-Billing data.
Self-billing is an arrangement between a supplier and a customer in which the customer prepares the
supplier’s invoice and forwards a copy to the supplier with the payment.
This file is processed through an external converter (GENTRAN), and transformed into an IDoc.

Six Steps of Self billing Process:

Customer creates and forwards the credit advice note via Electronic Data Interchange (EDI) to Bosch.
Bosch provides the delivery note that is subsequently used on the Selfbilling document. If there is
deviation in the values, then Bosch manually corrects the items through:
A credit memo request for quantity correction
A retro-billing for price correction
Bosch receives both the credit advice note and the payment advice note from the customer.

Advantages of Cash Management:

The benefits of the Cash Management module are:
1: Monitoring Cash Flow
2: Increasing visibility and control on Accounts Receivable

The Cash Management module controls the flow of cash by:

Incoming Payments
Dunning

A Credit Memo is mandatory for

- Posting of incoming payments
- Settlement of receivables
Clearing of Customer Account involves
- Manual entry of incoming payments from the customers
- Flat file, with details of customer payment, received from the bank

Dispute Management:
Controls and streamlines Dispute Cases by storing and organizing all the related information.
Dispute Case
A Dispute Case is a scenario where a receivables-related or a payment-related dispute arises between
Bosch and a customer.
Supplier
Customer
Dispute Case
Missing Payments
Incorrect Invoices
Incorrect Credits
Short Deliveries
Quality Issues
Dispute Case
Dispute Case
Process a dispute

Process Flow of Dispute Case

The steps involved in Dispute Case Management are:
Dispute Case
Creation
Processing of the Dispute Case consists of various steps like:
- Entering occasional Processor
- Sending an automated e-mail to the Processor
- Creating a work item
- Processing a work item
Dispute case processing
Dispute Case Closing

http://sarthakmohanty01.blogspot.com/2018/07/automotive-template-sap-model.html