LO Core Config 46B R2

SAP SMESAP SMESAP SMESAP SMECore ConfigurationCore ConfigurationCore ConfigurationCore Configuration

LogisticsLogisticsLogisticsLogistics

Version 4.6B R2.00Version 4.6B R2.00Version 4.6B R2.00Version 4.6B R2.00

SAP AG 2000

General Settings

4.6B R2.00

Contents

General Settings ......................................................................................................... 5Factory Calendar .......................................................................................................... 5

Enterprise Structure................................................................................................... 5Definition....................................................................................................................... 5Assignment ................................................................................................................... 7

Financial Accounting ............................................................................................... 10Global Settings ........................................................................................................... 10Special Purpose Ledger ............................................................................................. 10

Controlling................................................................................................................. 10Profitability Analysis.................................................................................................... 10Profit Centre Accounting............................................................................................. 13

Logistics – General .................................................................................................. 13Material Master........................................................................................................... 13Business Partner ........................................................................................................ 16Batch Management .................................................................................................... 18Logistics Information System (LIS)............................................................................. 20

Sales and Distribution.............................................................................................. 21Master Data ................................................................................................................ 21Basic Functions .......................................................................................................... 24Sales........................................................................................................................... 40Foreign Trade/Customs.............................................................................................. 46Billing .......................................................................................................................... 49

Materials Management ............................................................................................. 51Consumption Based Planning .................................................................................... 51Purchasing.................................................................................................................. 53Inventory Management and Physical Inventory ......................................................... 60Valuation and Account Assignment............................................................................ 64Invoice Verification ..................................................................................................... 69

Logistics Execution.................................................................................................. 70Shipping...................................................................................................................... 70

Appendix A - Delivered Master Data..................................................................... 79Customers Master Data.............................................................................................. 79Tax Records ............................................................................................................... 79Batch Determination Class ......................................................................................... 79Purchase Order Release Strategy Class ................................................................... 79

Appendix B - User Exits......................................................................................... 81Extending Material Master using Create transaction ................................................. 81Authorisation to delete Deliveries............................................................................... 81Source Plant determination in Sales Order ................................................................ 82Create Deliveries Report Variants.............................................................................. 82Profit Centre Substitution............................................................................................ 82Eligibility of Invoice Line Items for Intrastat reporting................................................. 83

Appendix C - Transaction Variants....................................................................... 84Create Purchase Requisition (ME51)......................................................................... 84

General Settings

Configuration Guide

Create Consignment Purchase Order (YPOCNS)......................................................84Total Material Planning (MD01) ..................................................................................84Individual Material Planning (MD03) ...........................................................................84Create Stock Transport Order (ME27)........................................................................84Create Inquiry (VA11) .................................................................................................84Create Quotation (VA21) ............................................................................................85Create Sales Order (VA01).........................................................................................85Create Pro-Forma Invoice (Y_SED_43000046) .........................................................86Sales Planning (KEPM) ..............................................................................................86Sales Profitability Analysis (Y035) ..............................................................................86Plan V’s Actual Report (Y036) ....................................................................................86Customer Contribution Report (Z420).........................................................................86Material Contribution Report (Z421) ...........................................................................86Create Stock Material (YS_MM01_ZMT1)..................................................................86Create Non-Stock Material (YS_MM01_ZMT2)..........................................................87Create No Value Stock Material (YS_MM01_ZNVS)..................................................87Create Service Material (YS_MM01_ZSER) ..............................................................87Create Third-Party Material (YS_MM01_Z3RD).........................................................88Create Consignment Material (YS_MM01_CONS) ....................................................88Create Sales BoM Header (YS_MM01_SBOM) .........................................................88Create Competitive Product (MMW1).........................................................................89Create Alternative Product Code (VB11)....................................................................89Create Sales BoM (Y_SED_43000135) .....................................................................89Create Sold-to Party (Z0001)......................................................................................89Create Ship-to Party (Z0002)......................................................................................89Create Payer (Z0003) .................................................................................................89Create Bill-to Party (Z0004) ........................................................................................90Create Sold-to Party – Manual Number (ZZ001)........................................................90Create Ship-to Party – Manual Number (ZZ002)........................................................90Create Payer – Manual Number (ZZ003) ...................................................................90Create Bill-to Party – Manual Number (ZZ004) ..........................................................90Create One-Time Customer (Y030)............................................................................91Create Prospect (Z0005) ............................................................................................91Convert Prospect to Customer (XD07) .......................................................................91Create Competitor (Z0006) .........................................................................................91Create Vendor (XK01) ................................................................................................91Create Vendor – Manual Number (YXK01_1) ............................................................92Create Employee (YXK01_2)......................................................................................92Create One-Time Vendor (YXK01_3) .........................................................................92

Appendix D - Activity Groups ................................................................................93YS_LO_CUSTSERREP (Customer Services Representative) .................................93YS_LO_SDCLERK (Delivery Clerk) ..........................................................................93YS_LO_DELDELETE (Delivery Deletion)..................................................................93YS_LO_PAADMIN (Profitability Analysis Administrator) ...........................................93YS_LO_PURCHCLERK (Purchasing Clerk)..............................................................93YS_LO_POCLERK (Purchase Order Release – Clerk) ............................................93YS_LO_POMANAGER (Purchase Order Release – Manager) ................................93YS_LO_BUDGETMGR (Purchase Order Release – Budget Manager) ....................93YS_LO_FINANCEDIR (Purchase Order Release – Finance Director)......................94YS_LO_MANDIR (Purchase Order Release – Managing Director) ..........................94YS_LO_STATREP (Statutory Reporting) ..................................................................94

General Settings

4.6B R2.00

YS_LO_STOCKCLERK (Stock Clerk)....................................................................... 94YS_LO_STOCKPLNR (Stock Planner) ..................................................................... 94YS_LO_CCSTOCKCONTROLLER (Cycle Counting Analysis & Approve) .............. 94YS_LO_CCSTOCKCLERK (Cycle Counting Results Entry)..................................... 94YS_LO_CCSTOCKDISPLAY (Cycle Counting Display Only)................................... 94YS_LO_IMPLEMENTOR (Implementor) ................................................................... 94

General Settings

Configuration Guide

General Settings

Factory CalendarThe following Factory Calendars are allowed :

GB Great Britain standard@2 Great Britain Mon-Sat working week@3 Great Britain Mon-Sun working week@4 Great Britain 365/366 working daysIE Republic of Ireland standard

Calendar ‘GB’ contains a Mon-Fri working week excluding Public Holidays.

Calendars ‘@2’ and ‘@3’ are copied from ‘GB’ but with a Mon-Sat and Mon-Sun workingweek respectively.

Calendar ‘@4’ contains no non-working days or Public Holidays.

Enterprise Structure

DefinitionLogistics – GeneralValuation Level

Material stocks are valuated at the Plant level.

Plant

64 Plants are provided. These are numbered :

0001 – 00101001 – 10502000, 3000, 4000 & 5000

All of these Plants (except for Plant 0001) contain the following values :

Field Value

Name1 Plant nnnn (where nnnn is Plant Code)

Language Key EN

Country Key GB

Factory Calendar GB (i.e. UK Standard)

Plant 0001 has Factory Calendar ‘@2’ (i.e. Mon-Sat working week) because this Plant isdesigned to be used with the Manufacturing module and a Mon-Sat working work ismost common in Manufacturing industries.

The Plant Name and Address fields are maintained during each CustomerImplementation.


4.6B R2.00

Location

Locations (not to be confused with Storage Locations) are not used in Logistics. They areonly used for Asset Accounting.

Division

50 Divisions numbered 01 – 50 are provided. The Division Names are maintainedduring each Customer Implementation.

Sales and DistributionSales Organisation

5 Sales Organisations numbered 0001 – 0005 are provided.

All of these Sales Organisations contain the following values :

Field Value

Name Sales Org. nnnn (where nnnn is Sales Org. code)

Statistics currency GBP

Address Text ZORG1_SENDER

Header Text ZORG1_HEADER

Footer Text ZORG1_FOOTER

Greeting Text ZORG1_SIGNATURE

The Address Text contains the Sales Org. name and address and is printed on OrderConfirmations, Cash Sale Invoices, Delivery Notes & Invoices.

The Footer Text can contain any supplementary information (e.g. Company Registrationnumber) and is printed on the bottom of Order Confirmations, Cash Sale Invoices,Delivery Notes & Invoices.

The Header Text and Greeting Text are not used.

Note, these texts are typically not required if pre-printed stationary is used.

The Sales Organisation Names and Standard Texts are maintained during eachCustomer Implementation.

Distribution Channels

50 Distribution Channels numbered 01 – 50 plus Distribution Channel SV are provided.

Distribution Channel ‘50’ is reserved for Internet Sales and Distribution Channel ‘SV’ isreserved for Service Order billing.

The Division Names are maintained during each Customer Implementation.

Sales Office

Sales Offices are not used.

Sales Group

Sales Groups are not used.


Configuration Guide

Materials ManagementStorage Location

10 Storage Locations numbered 0001 – 0010 are provided in Plants 0001 - 0010.

5 Storage Locations numbered 0001 – 0005 are provided in all other Plants.

Storage Location 0005 is not relevant for MRP in all Plants.

The Storage Location Names are maintained during each Customer Implementation.

Purchasing Organisation

5 Purchasing Organisations numbered 0001 – 0005 are provided.

The Purchasing Organisation Names are maintained during each CustomerImplementation.

Logistics ExecutionShipping Point

For each Plant there is an identically numbered Shipping Point.

All of the Shipping Points contain the following values :

Field Value

Name Shipping Point nnnn (where nnnn is Shipping PointCode)

Country GB

Departure Zone 0000000001

Factory Calendar GB (i.e. UK Standard)

Working Times 1-SHIFT

Loading Times Do not determine Loading Times

Pick/Pack Times Do not determine Pick/Pack Times

The default Factory Calendar and Working Times specify a Mon-Fri working week from0800 to 1700 (excluding public holidays). This can be changed to a Mon-Sat (excludingpublic holidays), Mon-Sun (excluding public holidays) or 365/366 working days/year.

Loading Times and Pick/Pack Times are not used in Delivery Scheduling.

The Text Forms are not used.

The Shipping Point Name is maintained during each Customer Implementation.

AssignmentLogistics – GeneralPlant to Company Code

Plants 0001 – 0010 and 1001 – 1050 are assigned to Company Code 0001.

Plants 2000, 3000, 4000 & 5000 are assigned to Company Codes 0002, 0003, 0004 & 0005respectively.


4.6B R2.00

Sales and DistributionSales Organisation to Company Code

Sales Organisations 0001, 0002, 0003, 0004 & 0005 are assigned to Company Codes 0001,0002, 0003, 0004 & 0005 respectively.

Distribution Channel to Sales Organisation

Distribution Channels 01 –50 and SV are assigned to Sales Organisation 0001.

Distribution Channels 01 and SV are assigned to Sales Organisations 0002, 0003, 0004 &0005.

Division to Sales Organisation

Divisions 01 – 50 are assigned to Sales Organisations 0001, 0002, 0003, 0004 & 0005.

Sales Area

A Sales Area has been defined for the following combinations of Sales Organisation,Distribution Channel and Division :

Sales Organisation Distribution Channel Division

0001 01 – 50, SV 01 – 50

0002 01, SV 01 - 50

0003 01, SV 01 - 50

0004 01, SV 01 - 50

0005 01, SV 01 - 50

Therefore, there are a total of 2,550 Sales Areas for Sales Organisation 0001 and 100 foreach of the other 4 Sales Organisations.

Plants to Sales Organisation/Distribution Channel

Plants 0001 – 0010 and 1001 – 1050 are assigned to Sales Organisation 0001 withDistribution Channels 01 – 50 & SV.

Plant 2000 is assigned to Sales Organisation 0002 with Distribution Channels 01 & SV.




Sales Area to Credit Control Area

This assignment is not used. The assignment at the level of Company Code is sufficient.

Business Area

There is no automatic Business Area assignment in a Sales Order.

Materials ManagementPurchasing Organisation to Company Code

Purchasing Organisations 0001, 0002, 0003, 0004 & 0005 are assigned to Company Codes0001, 0002, 0003, 0004 & 0005 respectively.


Configuration Guide

Plant to Purchasing Organisation

Plants 0001 – 0010 and 1001 – 1050 are assigned to Purchasing Organisation 0001.

Plant 2000 is assigned to Purchasing Organisation 0002.




Logistics ExecutionShipping Point to Plant

Each Shipping Point is assigned to the Plant of the same number. For example, ShippingPoint 0001 is assigned to Plant 0001.

Financial Accounting

4.6B R2.00

Financial Accounting

Global SettingsTax on Sales/PurchasesPosting

(1) Tax AccountsTax on sales (i.e. transaction MWS) is posted to account 207000 for all Output Tax Codes.

Tax on purchases (i.e. transactions NAV & VST) is posted to account 143030 for all InputTax Codes.

Special Purpose LedgerBasic SettingsUser Exits

Module Pool ‘YGGBS000’ has been assigned to Application Area ‘GBLS’ (Exits forsubstitution).

Module Pool ‘YGGBS000’ has been copied from ‘RGGBS000’ and has been used to defineProfit Centre Substitution Exit ‘Y901’ (see below).

Controlling

Profitability AnalysisPlease also refer the Financial Controlling Core Configuration Guide.

Master DataCharacteristics Derivation

The following Characteristics are derived via a Material Master (General Data) lookupusing the Material Number:

Material Group

The following Characteristics are derived via a Material Master (Sales Data) lookupusing the Material Number, Sales Organisation and Distribution Channel :

Material Pricing Group

The following Characteristics are derived via a Customer Master (General Data) lookupusing the Customer number :

IndustryCountryRegion

Controlling

Configuration Guide

The following Characteristics are derived via a Customer Master (Sales Data) lookupusing the Customer, Sales Organisation, Distribution Channel and Division :

Sales DistrictCustomer GroupPrice List TypeCustomer Group 1 – 5Customer Price Group

The following Characteristics are derived via a Sales Order (Header Data) lookup usingthe Sales Order Number :

Order Reason

All other Characteristics are derived using standard rules.

There are 2 derivation rules that are only used for Service Orders. Please refer to theService Core Configuration Guide for further details.

PlanningInitial Steps

In Operating Concern 0001 the following Record Types use Number Range 0200000000 –0299999999 :

F Billing Data

Note, all planning data is entered using Record Type ‘F’.

Flows of Actual ValuesInitial Steps

In Operating Concern 0001 the following Record Types use Number Range 0100000000 –0199999999 :

C Order/Project SettlementF Billing Data

Note, Record Type ‘C’ is used when settling 3rd-party Orders.

Transfer of Billing Documents

(1) Value FieldsPricing Condition Types are assigned to Value Fields as follows :

Controlling

4.6B R2.00

Pricing Condition Type Value field

PR00 ERLOS (i.e. Revenue)

EK01 ERLOS (i.e. Revenue)

PPAR ERLOS (i.e. Revenue)

PPSV ERLOS (i.e. Revenue)

HD00 AUSFR (i.e. Outgoing Freight)

K004 VVDIS (i.e. Discount)






Z001 VVDIS (i.e. Discount)




ZTOV VVDIS (i.e. Discount)

HB00 VVSUR (i.e. Surcharges)

Z030 VVSUR (i.e. Surcharges)

VPRS VVCOG (i.e. Cost of Goods Sold)

(2) Quantity FieldsThe Billed Quantity (FKIMG) is passed to the Quantity field in CO-PA.

(3) Reset Value/Quantity FieldsThe Billing Quantity (VVBQT) and Cost of Goods Sold (VVCOG) Value Fields are reset(i.e. not filled) for Credit Memos and Debit Memos because these Billing Types do notaffect the original quantity billed or the cost of those goods.

Order Settlement

Settlement Profile ‘ZSD1’ is used for settlement of 3rd-party Sales Orders. This Profileuses Allocation Structure ‘Z1’ and PA Transfer Structure ‘Z1’. 3rd-party Sales Orders aresettled to CO-PA only.

PA Transfer Structure ‘Z1’ assigns costs and revenue collected on 3rd-party Sales Ordersto Value Fields as follows :

Logistics – General

Configuration Guide

Source Cost Elements Target Value Field

500000 – 505000 VVCOG (i.e. Cost of Goods Sold)

400000 – 420000 ERLOS (i.e. Revenue)

450000 VVDIS (i.e. Discount)

700050 AUSFR (i.e. Outbound Freight)

The Quantity Billed is assigned to Value Field VVBQT.

Note, Costs (i.e. Cost Elements 500000 – 505000) are collected on 3rd-party Sales Orderswhen the Vendor Invoice is processed. Revenue is collected when the Sales Order isbilled.

Allocation Structure ‘Z1’ is simply used to define that the Debit Cost Element should bethe same as the Settlement Cost Element. Therefore, a settled 3rd-party Sales Order willhave identical reversing entries for each settled item.

Profit Centre AccountingAssignment to Profit CentresSales Orders

Substitution Y_PRCTR specifies a new rule for determining the Profit Centre in a SalesOrder. This Substitution uses an exit (Y901) which is documented in Appendix B – ProfitCentre Substitution.

In summary, the Plant from the user’s Parameter ID (if present) is used to determine theProfit Centre regardless of the delivering Plant. Thus, each user can effectively have adefault Profit Centre that will override the Profit Centre determined via the deliveringPlant. For users without a Plant Parameter ID the normal rule will apply.

Substitution Y_PRCTR is not activated by default and must be activated via the LogisticsImplementation menu if required.


Material MasterConfiguring the Material Master

5 customised screen layouts (i.e. Screen Sequences) have been created. The main designobjective was to reduce the number of screens and thus the complexity of maintainingMaterial Masters.

The Screen Sequence used when maintaining a Material depends on the Material Type ofthe Material as follows :


4.6B R2.00

Screen Sequence Material Types

Z2 WETT (i.e. Competitor’s Material)YBOM (i.e. Sales BoM Header)ZMT2 (i.e. N0n-stock Item)ZSER (Service Material)

Z3 ZMT1 (i.e. Stock Item)ZNVS (i.e. No-Value Stock Item)Z3RD (i.e. 3rd-party Material)

YF YFRT (i.e. Manufactured Material)

YH YHLB (i.e. Component Material)

YR YROH (i.e. Raw Material)

All Create, Change & Display transactions use Transaction Screen Reference ’01’. UserScreen References and Industry Screen References are not used.

Screen Sequences Z2 and Z3 are almost identical. The only difference is that ScreenSequence Z3 contains an extra screen (i.e. Screen 60 Document Data). Screen SequenceZ3 is used for Materials that are either physically stocked (e.g. ZMT1 & ZNVS) or forMaterials where some re-order data needs to be maintained for them (e.g. Z3RD).

Screen Sequence Z3 contains the following screens in the following sequence :

Main Screens Additional Screens

07 Basic Material Data 40 Description

23 Batch Managed 41 Units of Measure

09 Sales Data 1 57 Administrative Data

11 Sales Data 2 64 Additional EAN’s

13 Sales Text 60 Document Data

14 Purchasing Data 42 Basic Data Text

16 Purchasing Text 62 Inspection Text

15 Foreign Trade Data 63 Internal Comment

26 Reorder Data 48 Consumption

18 Storage Data 81 Proportion/Product Unit

24 Plant Stock

22 Accounting Details

Note, Screen 23 (Batch Managed) is simply the standard “Classification” screen andScreen 26 (Reorder Data) is based on the standard “MRP 1” screen.

Screen Sequences YF, YH & YH are only used by the Manufacturing Material Types.


Configuration Guide

Basic SettingsMaterial Types

Material Type ‘ZMT1’ (Stock Item) is used for standard stock items that are managedfrom both a quantity and a financial point of view.

Material Type ‘ZNVS’ (No-value stock item) is used for products that are managed byquantity only (typically low value items). These products are “consumed” (e.g. toexpense account/cost centre) at the time of Goods Receipt and therefore would neverappear in the Balance Sheet. The sales process is unchanged for these items.

Material Type ‘ZMT2’ (Non-stock Item) is used for products that are not managed byquantity or by value. They are also “consumed” (e.g. to expense account/cost centre) atthe time of Goods Receipt. They can still be sold to customers but are assumed to beinfinitely available and are not relevant for picking.

Material Type ‘ZSER’ (Services) is used for service-related products (e.g. consulting fees)that are not managed as physical inventory.

Material Type ‘Z3RD’ (3rd-party Items) is used for products that are supplied direct toCustomer from Vendor.

Material Type ‘YBOM’ (Sales BoM Header) is used for the definition of the completeproduct when using Sales BoM’s.

Key configuration points to note :

• Value Updating has been switched off for Material Type ZNVS.

• Quantity and Value updating have both been switched off for Material TypeZMT2.

• All of the above Material Types can only use external Purchase Orders. InternalProduction Orders cannot be used.

The allowable User Departments for each Material Type are :


4.6B R2.00

ZMT1 ZMT2 ZNVS ZSER Z3RD YBOM

Accounting ✔ ✔ ✔ ✔ ✔

Classification ✔ ✔

MRP ✔ ✔

Purchasing ✔ ✔ ✔ ✔ ✔

Basic Data ✔ ✔ ✔ ✔ ✔ ✔

Storage ✔ ✔

Sales ✔ ✔ ✔ ✔ ✔ ✔

Plant Stocks ✔ ✔

St. Loc. Stocks ✔ ✔

Settings for Key FieldsMaterial Groups

A standard set of Material Groups is supplied.

These can be changed during each Customer Implementation.

Business PartnerCustomersControl

The following Customer Account Groups are provided :

Account Group Description

0001 Sold-to party

0002 Ship-to party

0003 Payer

0004 Bill-to party

0005 Prospect

0006 Competitor

Z001 Sold-to Party (manual number)

Z002 Ship-to Party (manual number)

Z003 Payer (manual number)

Z004 Bill-to Party (manual number)

CPDA One-time Customer

ZDIS Distribution Plant

Account Groups 0001 – 0006 & CPDA are based on standard Account Groups. The mainchanges are :


Configuration Guide

• Cash Management Group (Account Management view) is mandatory.

• Sort Key (Account Management view) is mandatory.

• Indicate Payment History (Payment Transactions view) is mandatory.

• Customer Statistics Group (Sales view) is mandatory to ensure all Customersare updated in SIS.

• Price list Type (Sales view) is mandatory because the only Access Sequencethat is used with Pricing Condition PR00 contains this field as a key field.

• Account Assignment Group (Billing view) is mandatory to ensure revenueaccount determination never fails to find an account.

Account Groups Z001 – Z004 are identical copies of Account Groups 0001 – 0004respectively.

Account Group ZDIS is used for the “dummy” Customer Master that must be createdfor the receiving Plant in a Stock Transport Order. These Customers are created duringthe installation via CATT YS_DISTRIBUTION_CUSTOMER. Refer to Appendix A forfurther details.

Account Groups Z001 – Z004, CPDA and ZDIS use external numbering.

All other Account Groups use internal numbering (1 – 99999).

VendorsControl

The following Vendor Account Groups are provided :

Account Group Description

ZVND Vendor (manual number)

VEND Vendor

YEMP Employees

ONE One-time vendor

Account Group VEND is based on standard Account Group 0001. The main changes are:

• Sort Key (Account Management view) is mandatory.

• Terms of Payment (Payment Transactions and Purchasing Data views) ismandatory.

• Payment Methods (Payment Transactions view) is mandatory.

• Invoice Verification Tolerance Group (Payment Transactions view) ismandatory.

Account Group ZVND is an identical copy of Account Group VEND.

Account Group ONE is based on standard Account Group CPD.


4.6B R2.00

Account Group ZVND uses external numbering.

Account Group VEND uses internal numbering (1 – 99999).

Account Group YEMP uses internal numbering (300000 – 399999).

Account Group ONE uses internal numbering (100000 – 199999).

Batch ManagementBatch Level

Batches are defined to be unique at the Plant level.

Batch Number Assignment

Automatic batch numbering is inactive.

Creation of New Batches

Batches cannot be created automatically in Production Orders.

New batches can be created manually during a Goods Receipt (for all Goods ReceiptMovement Types). There is no check on the entered Batch number.

New batches can also be created manually via the “Create Batch” Master datatransaction for all Material Types. There is no check on the entered Batch number.

Batch Classification Value Assignment

The following Characteristics are used in Batch Classes :

• LOBM_VFDAT Expiration date, shelf life

• Y_BIN Storage Bin

Standard Characteristics LOBM_VFDAT is automatically populated during thefollowing Movement Types :

101 Goods Receipt into unrestricted stock501 Goods Receipt without Purchase Order into unrestricted stock505 Goods Receipt without Purchase Order into blocked stock521 Goods Receipt without Production Order into unrestricted stock525 Goods Receipt without Production Order into blocked stock561 Initial entry of unrestricted stock balance565 Initial entry of blocked stock balance

Characteristic Y_BIN must be manually maintained.

Batch Determination and Batch Check

Automatic Batch Determination and Batch Checking is only used in SD. It is notactivated for any Sales Order Items but is activated for the following Delivery ItemCategories :

BVN Cash SaleBVNN Cash Sale (free of charge)NLN Stock Transport ItemREN ReturnRENN Return (free of charge)TAN Standard itemTANN Standard item (free of charge)


Configuration Guide

TAX Non-stock itemYBM1 BoM Customer Pick-up sub-itemYBM2 BoM Customer Pick-up non-stock sub-itemYBM3 BoM Pay & Subsequent Delivery sub-itemYBM4 BoM Pay & Subsequent Delivery non-stock sub-itemYBMX B0M Standard Order non-stock sub-itemYBOM BoM Standard Order sub-itemYTAN Pay & Subsequent Delivery itemYTAX Pay & Subsequent Delivery non-stock itemYTNN Pay & Subsequent Delivery item (free of charge)

Only one Search Procedure (SD0001) is used. It is assigned to the following SalesDocument Types in all Sales Areas :

OR Standard OrderBV Customer Pick-upYBV2 Pay & Subsequent Delivery

Search Procedure SD0001 contains standard Strategy Type SD01 which allows BatchDetermination Condition Records to be defined either for a combination of Customerand Material or simply by Material. SME only uses the Material Access Sequence.

A Selection Class (Y_FIFO) and Sort Sequence (Y_FIFO) are also used in the BatchDetermination procedure. However, these are both master data and are thereforeshipped via CATT’s rather than using Transport Requests. Refer Appendix A for furtherdetails.

When the Delivery is created the batch is automatically chosen based on FIFO. Ifinsufficient stock is available in a single batch then multiple batches will automaticallybe chosen. Note, there is no check to ensure that the batch has not expired.

Batch Where-Used List

Batch where-used list updating is activated for synchronous updating in all Plants.

Shelf-Life Expiration Date

The shelf-life expiry date check is active for Goods Receipts in all plants. The followingMovement Types are affected :

101 Goods Receipt into unrestricted stock501 Goods Receipt without Purchase Order into unrestricted stock505 Goods Receipt without Purchase Order into blocked stock521 Goods Receipt without Production Order into unrestricted stock525 Goods Receipt without Production Order into blocked stock

If neither the “Minimum Remaining Shelf Life” nor the “Total Shelf Life” is entered onthe Material Master then no check is performed during Goods Receipt. However, theBatch Expiry Date can still be entered and this date will be used during subsequent batchdetermination.

If the “Minimum Remaining Shelf Life” is entered on the Material Master then the“Batch Expiry Date” must be entered during Goods Receipt. Furthermore, this datemust be after the current date plus the minimum remaining shelf life.

If the “Minimum Remaining Shelf Life” and the “Total Shelf Life” are entered on theMaterial Master then the “Date of Production” must be entered during Goods Receipt.


4.6B R2.00

The “Batch Expiry Date” is automatically calculated from this date plus the “Total ShelfLife”. The same rules as above apply regarding the minimum remaining shelf life.

Note, it is not possible to enter the “Total Shelf Life” on the Material Master withoutentering the “Minimum Remaining Shelf Life”.

Set Material to Batch-Managed

Transaction YS_BATCH_CLASS has been created to automate the process of enabling aMaterial for Batch Management. This transaction executes ABAP programYS_BATCH_MGT which in turn calls the following CATT’s :

• YS_BATCH_CLASS

• YS_BATCH_MATERIAL

• YS_BATCH_IND

• YS_BATCH_DETERM_MAT

YS_BATCH_CLASS simply initialises the Class Type to ‘022’ (i.e. Batch) usingtransaction CL6A. Note, CL6A is not significant. It is simply a transaction where theClass Type can be entered and thus set as the default.

YS_BATCH_MATERIAL assigns Class Y_FIFO (of Class Type ‘022’) to an existingMaterial. This ensures that all Batches created for this Material inherit Class Y_FIFO.Transaction YS_MM02_BATCH is used rather than MM02 because the Standard Varianton MM02 suppresses the Classification view.

YS_BATCH_IND sets the Batch-Managed flag on an existing Material.

YS_BATCH_DETERM_MAT creates a Batch Search Strategy Condition Record for anexisting Material using Selection Class Y_FIFO and Sort Rule Y_FIFO.

Logistics Information System (LIS)Logistics Data WarehouseData Basis

(1) Information StructuresInformation Structure S501 (Sales Commissions) has been created in Application Area‘01’ (i.e. Sales) to enable reporting of revenue by Sales Employee. This information canbe used for calculating commission payments due. It is based on standard Info.Structure S001 but with the added Characteristic of Sales Employee.

Note, this information is also available via CO-PA. The only difference is that S501 isalso updated with ordered revenue (as well as invoiced revenue).

Updating

(1) Updating DefinitionS501 is updated in the Sales Organisation Statistics Currency for the following businessevents :

VA Sales OrderVD Billing Document

Sales and Distribution

Configuration Guide

(2) Updating ControlThe following Information Structures are used :

Application Information Structure

01 (Sales) S001 Customer

01 (Sales) S501 Sales Commission

02 (Purchasing) S011 Purchasing Groups

02 (Purchasing) S012 Purchasing

03 (Stock) S031 Movements

03 (Stock) S032 Stock

The Period Unit for updating S001 and S501 is the Posting Period from the CompanyCode. All other Information Structures are update in calendar month periods.

The Customer Statistics Group and Material Statistics Group indicators are automaticallyset in the Customer and Material masters respectively via Transaction Variants in themaintenance transactions. Refer to Appendix C for further details.

The Statistics Currency for Sales Organisations 0001 – 0005 is ‘GBP’.


Master DataCommon Distribution Channels

Common Distribution Channels have been defined such that Customer/Material Masterdata and Pricing Conditions created for Distribution Channel ‘01’ are also valid forDistribution Channels 02 – 50.

Note, this does not include Distribution Channel ‘SV’ which must be maintainedseparately.

The definition of common Distribution Channels can be changed during each CustomerImplementation if, for example, different prices are required in each DistributionChannel.

Common Divisions

Common Divisions have been defined such that Customer Master data and PricingConditions created for Divisions ‘01’ are also valid for Divisions 02 – 50.

The definition of common Divisions can NOT be changed during each CustomerImplementation.


4.6B R2.00

Business PartnersCustomers

(1) Industry SectorIndustry Sector can be used for reporting in CO-PA. The following standard IndustrySectors are supplied :

Industry Sector Description

0008 Legal

0010 Advertising

0020 Agriculture

0030 Defence

0040 Education

0050 Entertainment

0060 Government

0070 Healthcare

0090 Manufacturing

0100 Mining

0110 Other

0120 Retail

0130 Technology

0140 Transport

0150 Travel & Tourism

These can be changed during each Customer Implementation and maintained at anytime via the Settings menu option.

(2) Customer GroupCustomer Group can be used for reporting in CO-PA. The following standard CustomerGroups are supplied :

Customer Group Description

01 Industry

02 Retail



Configuration Guide

(3) Sales DistrictSales District can be used for reporting in CO-PA. The following standard Sales Districtsare supplied :

Sales District Description

000001 Northern region

000002 Southern region


(4) Reserve Fields (Customer Groups 1 – 5)Customer Groups 1 – 5 can be used for reporting in CO-PA. No standard values aresupplied.

These can be entered during each Customer Implementation and maintained at any timevia the Settings menu option.

(5) Terms of PaymentA standard set of Payment Terms has been supplied. These can be changed during eachCustomer Implementation and maintained at any time via the Settings menu option.

Instalment Plans are also allowed. Payment Term ‘0009’ is an example of an InstalmentPlant payable in 3 instalments.

(6) IncotermsThe standard SAP Incoterms are supplied unchanged.

Contact Persons

Standard SAP values are supplied for the following Contact Person fields :

• Department

• Function

• Decision Authority

• Call Frequency

• Buying Habits

• VIP Indicator

Values for these fields cannot be used.

Contact Person Attributes 1 – 10 are also used. These can be entered during eachCustomer Implementation and maintained at any time via the Settings menu option.


4.6B R2.00

Basic FunctionsPricingPricing Control

(1) Pricing Procedure DeterminationPricing Procedure RVAA02 is determined for all Logistics Sales Document Types.

Pricing Procedures ZSER01 and ZSER02 are used only in Service Management. Refer tothe Service Core Configuration Guide for further details.

Pricing Procedure YPRCAT is used only in CRM. Refer to the CRM Core ConfigurationGuide for further details.

(2) Pricing Procedure

(a) Pricing Conditions

Pricing Procedure RVAA02 contains the following Pricing Conditions :

(i) EK01 (Actual Costs)

EK01 is only used for transferring actual costs from Service Orders during billing andcreation of service quotations. This Condition Type is also defined on the Order Typesused by Service Management. Refer to the Service Core Configuration Guide for furtherdetails on pricing in Service Management.

(ii) PR00 (Price)

PR00 is the mandatory “base” price. The Access Sequence has been changed from PR00to ZPR1. ZPR1 has been optimised to only access the Customer/Material and Price ListType/Customer/Material tables.

(iii) PPAR (Settlement Price Item)

PPAR is only used when pricing Service Orders for any prices specified in the ServiceContract. Refer to the Service Core Configuration Guide for further details on pricing inService Management.

(iv) Z001 (Service Contract Material Discount)

Z001 is only used when pricing Service Orders for any Material Discounts specified inthe Service Contract. Refer to the Service Core Configuration Guide for further detailson pricing in Service Management.

(v) Z002 (Service Contract Price Group Discount)

Z002 is only used when pricing Service Orders for any Price Group Discounts specifiedin the Service Contract. Refer to the Service Core Configuration Guide for further detailson pricing in Service Management.

(vi) Z005 (Customer/Material Discount)


Configuration Guide

Z005 allows percentage discounts to be defined for combinations of Customer andMaterial.

(vii) K007 (Customer Discount)

K007 allows percentage discounts to be defined for individual Customers.

(viii) Z029 (Material Pricing Group Discount)

Z029 allows percentage discounts to be defined at the Material Pricing Group level.

(ix) K030 (Customer/Material Pricing Group Discount)

K030 allows percentage discounts to be defined for combinations of Customer andMaterial Pricing Group.

(x) K031 (Customer Price Group/Material Pricing Group Discount)

K031 allows percentage discounts to be defined for combinations of Customer PriceGroup and Material Pricing Group.

(xi) K032 (Customer Price Group/Material Discount)

K032 allows percentage discounts to be defined for combinations of Customer PriceGroup and Material.

(xii) HD00 (Freight Charge)

HD00 allows a freight rate to be manually added at the header level. The freight chargeis calculated by weight and therefore weight must be maintained for the enteredmaterials.

(xiii) HB00 (Order Surcharge)

HB00 allows a fixed amount to be manually added at the header level as an ordersurcharge.

(xiv) ZTOV (Total Order Value Discount)

ZTOV allows percentage discounts to be defined for combinations of Customer PriceGroup and Material Pricing Group. This Condition Type is a Group Condition and ituses a Value Scale basis. Therefore, discounts can be defined using Pricing Scales thatwill only apply if the total order value exceeds a pre-defined limit.

(xv) AMIW (Minimum Sales Order Value)

AMIW works in conjunction with Z030. AMIW allows a minimum sales order value tobe defined for individual Customers. Note, AMIW is statistical only. The minimumsales order value is stored in field XWORKE.

(xvi) Z030 (Minimum Value Surcharge)

Z030 allows a fixed amount to be defined that will be added as a surcharge if the totalorder value is less than the minimum defined in AMIW.


4.6B R2.00

Condition Value ‘901’ deactivates this condition if the Net Value is greater thanXWORKE. Requirement ‘902’ is used to ensure that the surcharge is only applied once(on to the first Order Item).

(xvii) SKTO (Cash Discount)

SKTO is the standard statistical condition for early payment discounts.

(xviii) MWST (Output Tax)

MWST is the standard condition for Output Tax.

(xix) VPRS (Cost)

VPRS is the standard statistical condition for cost of goods sold.

(b) Sub-totals

The following sub-totals are used for updating SIS :

1 Gross Value2 Net Value3 Net Value including Freight4 Freight

Note, Sub-totals 1 and 2 are also used to pass pricing details to the Online Store.

Sub-total 7 is not currently used but is reserved for future use with Rebate Agreements.

Sub-total A is used in Credit Management as the Credit Price.

Sub-total B is used for the Cost as per standard SAP.

Sub-total C is used for Intrastat reporting. For free items the cost price must be reportedas the “statistical price”.

Sub-total E is used by the Minimum Value Surcharge (Z030) condition. Refer above.

(3) Pricing by Item categoryPricing has been de-activated for the following Item Categories :

AGNN (Quotation)TANN (Standard Order)BVNN (Customer Pick-Up)YTNN (Pay & Subsequent Delivery)RENN (Return Order)

Price-Relevant Master data Fields

(1) Price List TypesPrice List Type is a mandatory key field when creating List Prices (i.e. Condition TypePR00). Customers must therefore have a valid Price List Type assigned for prices to becalculated correctly. The following standard Price List Types are supplied :


Configuration Guide

Price List Type Description

01 Wholesale

02 Retail

03 Direct

04 Other


(2) Customer Price GroupsCustomer Price Groups can be used to define Pricing Discounts for groups of Customers.The following standard Customer Price Groups are supplied :

Customer Price Group Description

01 Bulk Buyer

02 Occasional Buyer


(3) Material Price GroupsMaterial Price Groups can be used to define Pricing Discounts for groups of Materials.The following standard Material Price Groups are supplied :

Material Price Group Description

01 Normal

02 Spare Parts


Condition Exclusion

Condition Exclusion Group Z001 (Standard Discounts) contains the following PricingConditions :


4.6B R2.00

Condition Type Description

K007 Customer Discount

K030 Customer/Material Pricing Group Discount

K031 Customer Price Grp/Mat. Pricing Grp Discount

K032 Customer Price Group/Material Discount

Z005 Customer/Material Discount

Z029 Material Pricing Group Discount

Condition Exclusion Group Z002 (Contract Material Discounts) contains the followingPricing Conditions :


Z001 Contract-specific Material Discount

Condition Exclusion Group Z003 (Contract Material Pricing Group Discounts) containsthe following Pricing Conditions :


Z002 Contract-specific Material Pricing Group Discount

Pricing Conditions Z001 and Z002 are only used in Service Contracts for billing ServiceOrders. In a Service Contract you can define a contract-specific discount either for aMaterial (Z001) or for a Material Pricing Group (Z002).

The purpose of the Exclusion Groups is to ensure that Service Contract discountsoverride any other discounts instead of applying cumulatively.

Group Z002 excludes Group Z003 so that a contract-specific Material discount hasprecedence over a contract-specific MPG discount.

Group Z002 excludes Group Z001 so that a contract-specific Material discount overridesany "normal" discounts (e.g. customer/material).

Group Z003 excludes Group Z001 so that a contract-specific MPG discount alsooverrides any "normal" discounts.

Free Goods

There is no automatic determination of free goods. Free goods can only be specified bymanually changing the Item Category in the Sales Order. The following Item Categoriesare used for free goods :

AGNN (Quotation)TANN (Standard Order)BVNN (Customer Pick-Up)


Configuration Guide

YTNN (Pay & Subsequent Delivery)RENN (Return Order)

TaxesTax Determination Rules

Tax Category MWST is used for Country GB.

Customer Tax Class

The following Customer Tax Classes are provided for Tax category MWST :

Tax Class Description

0 Tax Exempt

1 Liable for Taxes

Material Tax Class

The following Material Tax Classes are provided for Tax category MWST :

Tax Class Description

0 No Tax

1 Full Tax

3 Service

Sales Tax Identification Number Determination

The VAT Registration Number and Tax Class are taken from the Sold-to Party.

Account Assignment/CostingRevenue Account Determination

(1) Material Account Assignment GroupsThe following Material Account Assignment Groups are provided :


4.6B R2.00

Account Assignment Group Description

01 Sales Revenue Group 1










This allows revenue to be reported under up to 10 different product groupings.

The Material Account Assignment Group descriptions can be changed during eachCustomer Implementation. Note, the corresponding G/L Account names would alsoneed to be changed.

(2) Customer Account Assignment GroupsThe following Customer Account Assignment Groups are provided :

Account Assignment Group Description

01 Domestic Revenues

02 Foreign Revenues

The Customer Account Assignment Group descriptions can NOT be changed duringeach Customer Implementation.

(3) G/L Account AssignmentG/L Account assignment is defined using 3 different Access Sequences.

Revenue (i.e. Account Key ERL) is assigned using the “Customer Account AssignmentGroup / Material Account Assignment Group / Account Key” Access Sequence asfollows :


Configuration Guide

Customer Account Assignment Group Material Account Assignment Group G/L Account

01 (i.e. Domestic Revenues) 01 (i.e. Sales Revenue Group 1) 400000

01 02 (i.e. Sales Revenue Group 2) 400010









02 (i.e. Foreign Revenues) 01 (i.e. Sales Revenue Group 1) 410000










Freight, Sales Deductions and Tax are assigned using the “Account Key” AccessSequence. Freight is assigned to G/L Account 700050, Sales Deductions to 450000 andTax to 207000.

Anything else (i.e. errors) is assigned to G/L Account 999000 using the “General” AccessSequence.

Availability Check and Transfer of RequirementsTransfer of Requirements

(1) Requirements ClassRequirements Class ‘Z39’ has been created specifically for use with 3rd-party Orders sothat all costs and revenues are collected on the Sales Order before being settled to CO-PA. This has the advantage that the actual costs (from vendor invoices) will be reportedin CO-PA rather than the standard or moving average cost from the Material Master.The disadvantage is that these Sales Orders must be manually settled.

Requirements Class Z39 has the following attributes :


4.6B R2.00

Field Value

Account Assignment Category E

Settlement Profile ZSD1

Account Assignment Category ‘E’ specifies that the Sales Document Item is the “CostCollector” and Settlement Profile ‘ZSD1’ defines how these costs are subsequentlysettled to CO-PA. Note, the Results Analysis Key has been removed.

(2) Requirements TypeRequirements Class ‘Z39’ is assigned to Requirements Type ‘Z039’.

(3) Determination of Requirements TypeRequirements Type ‘Z039’ is assigned to Item Category ‘TAS’ (i.e. 3rd-party Order).

(4) Requirements for Purchase OrdersRequirement ‘902’ has been created specifically for use with 3rd-party Orders. It wascopied from Requirement ‘102’ and an additional check on Delivery Block field included.

This check was necessary only in prior releases when “simple” credit limit checking wasused. Now that “automatic credit control” is used this extra check is no longer requiredand Requirement ‘102’ would suffice.

The Requirement should now be changed back to ‘102’.

Availability Check

(1) Availability Check with ATP Logic

(a) Checking Groups

The following standard Checking Groups only are allowed :

01 Daily Requirements02 Individual RequirementsKP No Check

(b) Default Values

Checking Group ‘02’ is defined as the default value for Material Types ZMT1, ZMT2 &ZNVS in all Plants. This same value is also set by the Transaction Variants for each ofthe “Create Material” transactions (non-Manufacturing materials only).

(c) Availability Check Control

The Availability Check Control defined for SD Orders includes the following :

Safety StockPurchase OrdersReservations


Configuration Guide

Sales RequirementsDeliveriesFirmed Planned OrdersProduction Orders (released or not)

All items outside the Replenishment Lead Time are confirmed automatically.

Note, Reservations are created by Service Orders and Production Orders.

The Availability Check Control defined for SD Deliveries includes the following :

Purchase OrdersReservationsDeliveriesProduction Orders (released or not)

Items outside the Replenishment Lead Time are not confirmed.

Note, the SD Deliveries check does not include Sales Requirements. Refer to OSS Note36520 for an explanation of why these have been excluded.

Output ControlOutput Determination

(1) Sales Documents

(a) Output Types

The following Sales Document Output Types are used :

BA00 Order ConfirmationRD03 Cash Sale Invoice

The following changes have been made to both Output Types :

• A new Access Sequence (Z002) is used that allows Output Condition records tobe defined by Sales Organisation, Distribution Channel & Sales Document Type.

• The Communications Strategy has been set to ‘CS01’ so that the output can besent via email if the Customer Master contains an email address.

• The Output Program has been changed to YS_RVADOR01. This program issimply a copy of RVADOR01.

The Output Forms for BA00 and RD03 have been changed to ZVORDER01 andZ_SD_CASH_SALE respectively. These are copied from standard Forms RVORDER01and SD_CASH_SALE respectively so that Customers can customise their output layouts.The associated Output Program (RVADOR01) has also been copied to keep the OutputProgram and Forms consistent.

(b) Output Determination Procedure

The following Output Procedures are used with Sales Documents :


4.6B R2.00

Output Procedure Output Type

V10000 (Order Output) BA00 (Order Confirmation)

V10001 (Cash Sales Output) RD03 (Cash Sale Invoice)

These procedures are assigned to the following Sales Document Types :

Sales Document Type Output Procedure

BV (Customer Pick-Up) V10001

CR (Credit Memo Request) V10000

DR (Debit Memo Request) V10000

OR (Standard Order) V10000

RE (Return Order) V10000

YBV2 (Pay & SubsequentDelivery)

V10001

(2) Billing Documents

(a) Output Types

The following Billing Document Output Types are used :

RD00 Invoice

The following changes have been made to RD00 :

• A new Access Sequence (Z001) is used that allows Output Condition records tobe defined by Sales Organisation, Distribution Channel & Sales Document Type.


• The Output Program has been changed to YS_RVADIN01. This program issimply a copy of RVADIN01.

• The Output Form has been changed to ZVINVOICE01. This Form is simply acopy of standard Form RVINVOICE01 so that Customers can customise theirinvoice layout. The associated Output Program (RVADIN01) has also beencopied to keep the Output Program and Form consistent.

(b) Output Determination Procedure

The following Output Procedure is used with Billing Documents :


V10000 (Billing Output) RD00 (Invoice)

This procedure is assigned to the following Billing Document Types :


Configuration Guide

Billing Document Type Output Procedure

F2 (Invoice) V10000

G2 (Credit Memo) V10000

L2 (Debit Memo) V10000

RE (credit for Returns) V10000

S1 (Cancellation of Invoice) V10000

Material DeterminationMaterial Determination Procedure

Material Determination has been configured to allow an entered Material to beautomatically substituted by another for a period of time.

The following Material Determination Procedure is used with Sales Documents :

Material Determination Procedure Condition Type

A00001 (Material Determination) A001 (Material Entered)

No changes have been made to this procedure or to Condition Type A001.

This procedures is assigned to the following Sales Document Types :

Sales Document Type Material Determination Procedure

BV (Customer Pick-Up) A00001

CR (Credit Memo Request) A00000

DR (Debit Memo Request) A00000

OR (Standard Order) A00000

RE (Return Order) A00000


A00001

Substitution Reasons

The only Substitution Reason that can be used is Z001 (Alternative Product Code). Z001has the following attributes :


4.6B R2.00

Field Value

Entry Pint original Material Number on all Output

Warning Issue warning before substituting Material

Strategy Automatic substitution

Outcome Item is replaced

Substitution Reason ‘Z001’ is automatically set via the Transaction Variant for the“Create Material Determination Condition record” transaction (VB11). Refer toAppendix C for further details.

Partner DeterminationCustomer

The Partner Determination Procedure used depends on the Customer Account Group asfollows :

Customer Account Group Partner Determination Procedure

0001 (Sold-to Party) ZAG

0002 (Ship-to Party) WE

0003 (Payer) RG

0004 (Bill-to Party) RE

0005 (Prospect) ZAG

0006 (Competitor) RE

Z001 (Sold-to Party – external) ZAG

Z002 (Ship-to Party - external) WE

Z003 (Payer – external) RG

Z004 (Bill-to Party – external) RE

CPDA (One-time Customer) ZAG

ZDIS (Distribution Plant) WE

Procedures WE, RG and RE are standard.

Procedure ZAG is copied from standard procedure AG and contains the followingPartner Functions :

SP Sold-to Party (mandatory)CP Contact PersonVN VendorBP Bill-to Party (mandatory)PY Payer (mandatory)CR Forwarding AgentPE Sales Employee


Configuration Guide

SH Ship-to Party (mandatory)ER Employee Responsible

Sales Document Header

All of the Sales Document Types use standard Partner Determination Procedure ‘TA’.This procedure has not been changed.

Sales Document Item

The standard assignments of procedures ‘N’ and ‘T’ have not been changed nor have theprocedures themselves.

Delivery

All of the Delivery Types use standard Partner Determination Procedure ‘LF’. Thisprocedure has not been changed.

Billing Header

All of the Billing Document Types use standard Partner Determination Procedure ‘FK’.This procedure has not been changed.

Billing Item

All of the Billing Items use standard Partner Determination Procedure ‘FP’. Thisprocedure has not been changed.

Text ControlCustomer

The following Text Types can be used with Customer Sales Text :

0001 Sales Note for Customer0002 Shipping Instructions0003 Selection for Shipping0004 Marketing Notes

Sales Document Header

(1) Text TypesThe following Text Types can be used with Sales Document Headers :

0001 Header0003 CommentsY001 Shipping Instructions

The Header Text Type is printed on Quotations, Order Confirmations and Invoices.

The Comments Text Types is for internal use only.

The Shipping Instructions Text Type is printed on Delivery Notes.

(2) Text ProcedureText Type 0001 (i.e. Header) is copied from Customer Text Type 0001 (i.e. Sales Note forCustomer).

Text Type 0003 (i.e. Comments) is manually entered.


4.6B R2.00

Text Type Y001 (i.e. Shipping Instructions) is copied from Customer Text Type 0002 (i.e.Shipping Instructions).

Sales Document Item

(1) Text TypesThe following Text Types can be used with Sales Document Items :

0001 Material Sales Text0003 Packing Note

The Material Sales Text Type is printed on Quotations, Order Confirmations andInvoices.

The Packing Note Text Type is printed on Picking Notes.

(2) Text ProcedureText Type 0001 (i.e. Material Sales Text) is copied from Material Text Type 0001 (i.e.Material Sales Text).

Text Type 0003 (i.e. Packing Note) is manually entered.

Delivery Header

(1) Text TypesThe following Text Types can be used with Delivery Headers :

0001 HeaderY001 Shipping Instructions

(2) Text ProcedureText Type 0001 (i.e. Header) is copied from Sales Header Text Type 0001 (i.e. Header).

Text Type Y001 (i.e. Shipping Instructions) is copied from Sales Header Text Type Y001(i.e. Shipping Instructions).

Delivery Item

(1) Text TypesThe following Text Types can be used with Delivery Items :

0001 Material Sales Text0003 Packing Note

(2) Text ProcedureText Type 0001 (i.e. Material Sales Text) is copied from Sales Item Text Type 0001 (i.e.Material Sales Text) or Material Text Type 0001 (i.e. Material Sales Text).

Text Type 0003 (i.e. Packing Note) is copied from Sales Item Text Type 0003 (i.e. PackingNote).


Configuration Guide

Billing Header

(1) Text TypesThe following Text Types can be used with Billing Headers :

0001 Header

(2) Text ProcedureText Type 0001 (i.e. Header) is copied from Sales Header Text Type 0001 (i.e. Header).

Billing Item

(1) Text TypesThe following Text Types can be used with Billing Items :

0001 Material Sales Text

(2) Text ProcedureText Type 0001 (i.e. Material Sales Text) is copied from Sales Item Text Type 0001 (i.e.Material Sales Text) or Material Text Type 0001 (i.e. Material Sales Text).

Log of Incomplete ItemsSales Header

Incompletion procedures have been assigned to Order Types as follows :

Sales Document Type Incompletion Procedure

BV (Customer Pick-Up) 11

CR (Credit Memo Request) Z2

DR (Debit Memo Request) Z1

OR (Standard Order) 11

RE (Return Order) Z2


11

Incompletion Procedure 11 is unchanged from the standard.

Procedures Z1 and Z2 are copied from procedures 14 and 15 respectively. The OrderReason field has been removed.

Sales Item

The Gross Weight field has been removed from the standard procedures.

Sales Schedule Line

No changes have been made.


4.6B R2.00

Credit Management/Risk ManagementCredit Management

(1) Assign Sales Documents and Delivery DocumentsAutomatic Credit Control is activated for the following Order Types :

OR Standard OrderYBV2 Pay & Subsequent Delivery

Automatic Credit Control is not activated for and Delivery Types.

(2) Automatic Credit ControlThe Automatic Credit Control check has been defined to perform a static check.

The customer's credit exposure may not exceed the established credit limit. The creditexposure is the total combined value of the following :

• Open sales documents

• Open delivery documents

• Open billing documents

• Open items (accounts receivable)

If the check fails the Sales order will be blocked.

Serial Numbers

Serial Number Profile 0001 has been defined and is the only profile that can be assignedto Materials (on the Sales Data 2 view). This profile specifies that :

• Equipment Masters are created with Equipment Category S

• Serial Numbers can be created during a business transaction (i.e. they do notneed to be pre-defined)

Serial Numbers must be entered for Business Transaction MMSL (i.e. GoodsMovements). An Equipment Master record will be automatically created.

Serial Numbers can be optionally entered in a Sales Order or a Delivery prior to GoodsIssue.

SalesSales DocumentsSales Document Header

(1) Sales Document TypesThe following Sales Document Types are used :


Configuration Guide

Sales Document Type Description

IN Inquiry

QT Quotation

OR Standard Order

BV Customer Pick-Up

YBV2 Pay + Subsequent Delivery

RE Return

CR Credit Memo Request

DR Debit Memo Request

DL Order for Replenishment Delivery

All of the above are standard Order Types with the exception of ‘YBV2’. This OrderType is like ‘BV’ in that it is a cash sale but also like ‘OR’ in that the goods aresubsequently shipped to the Customer.

Transaction Variants have been assigned to all of the above Order Types (except ‘DL’).Refer to Appendix C for further details. Note, these Variants are client-independentbecause only client-independent Variants are allowed.

(2) Assign Sales Areas to Sales Document TypesSales Document Type ‘DL’ is not allocated to any Sales Areas because it is never actuallyentered in a Sales Document.

All other Sales Document Types can be used in :

• Sales Organisations 0001 –0005

• Distribution Channels 01 – 50

• Divisions 01 – 50

Note, Sales Document Types ‘IN’, ‘QT’, ‘BV’ & ‘YBV2’ cannot be used in DistributionChannel SV (i.e. Service).

Sales Document Item

(1) Item CategoriesThe following Item Categories are used :


4.6B R2.00

Item Category Description

AFN Inquiry

AFX Inquiry Non-stock

AGN Quotation

AGNN Quotation Free of Charge

AGX Quotation Non-stock

TAN Standard

TANN Standard Free of Charge

TAS Standard 3rd-Party

TAD Standard Service

TAX Standard Non-stock

YTAQ Standard BoM Header

YBOM Standard BoM Sub-item

YBMX Standard BoM Non-stock Sub-item

BVN Customer Pick-up

BVNN Customer Pick-up Free of Charge

YTAX Customer Pick-up Non-stock

YTQ1 Customer Pick-up BoM Header

YBM1 Customer Pick-up BoM Sub-item

YBM2 Customer Pick-up BoM Non-stock Sub-item

YTAN Pay & Subsequent Delivery

YTNN Pay & Subsequent Delivery Free of Charge

YTAX Pay & Subsequent Delivery Non-stock

YTQ2 Pay & Subsequent Delivery BoM Header

YBM3 Pay & Subsequent Delivery BoM Sub-item

YBM4 Pay & Subsequent Delivery BoM Non-stock Sub-item

REN Return

RENN Return Free of Charge

G2N Credit Request

G2W Credit Request Service

L2N Debit Request

L2W Debit Request Service

(2) Item Category Groups


Configuration Guide

The following Item Category Groups are used :

Item Category Group Description

NORM Standard Item

BANS Third-Party Item

LEIS Service without Delivery

NLAG Non-stock Material

YBOM Sales BoM Header

Item Category Group ‘YBOM’ is used to create the header Material in a Sales BoM withthe following characteristics :

• Priced at header level

• Stocked at component level

• Assembled during picking/shipping

This is different from the two standard Sales BoM Item Category Groups (i.e. ERLA &LUMF) and therefore a new one was created.

(3) Default Values for Material TypeThe following default Item Category Groups for Material Types have been defined :

Material Type Item Category Group

ZMT1 NORM

ZMT2 NLAG

ZNVS NORM

ZSER LEIS

Z3RD BANS

YBOM YBOM

Note, these defaults are actually over-ridden by the values defined in the TransactionVariants for the various “Create Material” transactions. Refer Appendix C for furtherdetails.

(4) Assign Item CategoriesItem Categories are assigned as follows :


4.6B R2.00

Sales DocumentType

Item CategoryGroup

Usage Higher LevelItem Category

Item Category

NORM AFN

NLAG AFX

LEIS AFX

BANS AFN

IN

YBOM AFN

NORM AGN, AGNN

NLAG AGX

LEIS AGX

BANS AGN, AGNN

QT

YBOM AGN, AGNN

NORM TAN, TANN

NLAG TAX

LEIS TAD

BANS TAS

YBOM YTAQ

NORM YTAQ YBOM

OR

NLAG YTAQ YBMX

NORM BVN, BVNN

NLAG YTAX

LEIS TAD

YBOM YTQ1

NORM YTQ1 YBM1

BV

NLAG YTQ1 YBM2

NORM YTAN, YTNN

NLAG YTAX

LEIS TAD

BANS TAS

YBOM YTQ2

NORM YTQ2 YBM3

YBV2

NLAG YTQ2 YBM4

NORM REN, RENNRE

NLAG REN , RENN


Configuration Guide

BANS REN

NORM G2N

NLAG G2N

LEIS G2W

BANS G2N

CR

YBOM G2N

NORM L2N

NLAG L2N

LEIS L2W

BANS L2N

DR

YBOM L2N

Schedule Lines

The following Schedule Line Categories are used :

Schedule Line Category Description

AT Inquiry (No MRP)

BN Quotation (No MRP)

BT Quotation (No inventory mgt.)

CD Without Delivery

CN No Material Planning

CP MRP

CS Leg

CT No Inventory Mgt. / No Goods Issue

CX No Inventory Mgt.

DN Returns

Schedule Line Category ‘CS’ has been modified so that it uses Order Type ‘TP’ andAccount Assignment Category ‘Y’ (i.e. 3rd-party).

Copying ControlCopy Control

Copy Control has been defined for the following Billing Types to Sales Document Types:

BV � CRF2 � CRBV � DRF2 � DR


4.6B R2.00

BV � REF2 � RE

Copy Control has been defined for the following Sales Document Types to SalesDocument Types :

IN � QTBV � CROR � CRYBV2 � CROR � DRYBV2 � DRBV � REOR � REYBV2 � REQT � ORIN � OROR � OR

Requirements

Requirement ‘901’ has been created to prevent the main Batch item being copied from aBilling Document to a Sales Order when a Batch Split exists. The main Batch item has aquantity of 0 and is for information only.

This Item-level Requirement is used when copying the following Billing Types to SalesDocument Types :

BV � CRF2 � CRBV � DRF2 � DRBV � REF2 � RE

Foreign Trade/CustomsControl DataIncompleteness Schemas

The following Incompletion Schemas have been defined :

Z1 (Header Export)Z2 (Item Export)Z3 (Header Import)Z4 (item Import)

The following table summarises the required fields in each procedure :


Configuration Guide

Field Z1 Z2 Z3 Z4

Mode of Transport ✔ ✔

Business Transaction Type ✔ ✔

Commodity Code ✔ ✔

Country of Origin ✔

All the above procedures are assigned to Country ‘GB’. They are set to issue a warningonly during document entry.

Basic DataBusiness Transaction Types

(1) ExportsThe Business Transaction Type for exports is defaulted according to the Sales ItemCategory as follows :

Item Category Business Transaction Type

BVN (Cash Sale)L2N (Debit Request)TAN (Standard Item)TAS (Third-party Item)TAX (Non-stock Item)YTAN (Standard Item – P&D)YTAX (Non-stock Item – P&D)

10 (i.e. Standard Sales/Purchases)

G2N (Credit Request)REN (Return)

16 (i.e. Credit on Standard Sales/Purchases)

BVNN (Cash Sale Free of Charge)TANN (Free of charge Item)YTNN (Free of charge Item – P&D)

30 (i.e. Free Goods)

RENN (Return Free of charge) 36 (i.e. Credit on Free Goods)

(2) ImportsThe Business Transaction Type for imports is defaulted according to the Purchase OrderType and Purchasing Item category as follows :


4.6B R2.00

Order Type Item Category Business Transaction Type

PO ‘ ‘ (i.e. Standard)S (i.e. Third-party)

10 (i.e. Standard Sales/Purchases)

PO K (i.e. Consignment) 60 (i.e. No change of ownership)

Transportation DataDefault Values for Foreign Trade Header

The default Mode of Transport has been set to ‘1’ (i.e. Sea) for export to and import fromthe following Countries :

AT AustriaBE BelgiumDE GermanyDK DenmarkES SpainFI FinlandFR FranceGR GreeceIE IrelandIT ItalyLU LuxembourgNL NetherlandsPT PortugalSE Sweden


Statistical Values

For free items the cost price must be reported as the “statistical price”. This istransferred to Foreign Trade processing via field KOMP-GKWRT.

In Pricing Procedure RVAA02 the “Statistical Value” line calculates the cost price andplaces it in sub-total ‘C’ (i.e.KOMP-GKWRT).

Printing/Communication

Form YSD_EXPAIU has been copied from standard SAP Form SD_EXPAIU andcustomised to be compatible with the official Intrastat pre-printed stationery for Arrivals(C1500) and Dispatches (C1501).

Periodic DeclarationsControl Data

(1) Inclusion and Exclusion IndicatorsThe following Sales Order Item Categories have been excluded from Intrastatdeclarations :

G2W Credit Request for ServiceL2W Debit Request for ServiceTAD Service ItemTATX Text Item


Configuration Guide

The following Delivery Item Categories have been excluded from Intrastat declarations :

NLN Replenishment Delivery

Prior to Release 4.6 these indicators were only used for excluding items. Includingadditional items had to be done by adding the Item Categories to Include RVEXKUEI(refer to Appendix B for further details). The following Item Categories have beenincluded via this approach :

BVN Cash SaleBVNN Cash Sales Free of ChargeYTAX Non-stock Item – P&DYTAN Standard Item – P&DRENN Return Free of Charge

(2) Official Numbers for Declarations to AuthoritiesThe Intrastat Id number must be maintained against the relevant Company Id(s) duringeach Customer implementation.

BillingBilling DocumentsBilling Types

The following Billing Types are used :

Billing Type Description

F2 Invoice

BV Cash Sales

RE Credit for Returns

G2 Credit Memo

L2 Debit Memo

F5 Pro-forma for Order

S1 Cancellation of Invoice

S2 Cancellation of Credit Memo

SV Cancellation of Cash Sale

Billing Type ‘F2’ is used for Order and Delivery-related billing of Order Type ‘OR’.

Billing Type ‘BV’ is used for Order-related billing of Order Types ‘BV’ and ‘YBV2’.

Billing Types ‘RE’, ‘G2’ & ‘L2’ are used for Order-related billing of Order Types ‘RE’,‘CR’ & ‘DR’ respectively.

Billing Type ‘F5’ is used for producing pro-forma Invoices from Sales Orders.

Billing Type ‘S1’ is used for cancellation of Billing Types ‘F2’ and ‘L2’.


4.6B R2.00

Billing Type ‘S2’ is used for cancellation of Billing Type ‘RE’ and ‘G2’.

Billing Type ‘SV’ is used for cancellation of Billing Type ‘BV’.

Copying Control

(1) Copy ControlCopy Control has been defined for the following Delivery Types to Billing Types :

LF � F2

Copy Control has been defined for the following Order Types to Billing Types :

OR � F2OR � F5BV � BVYBV2 � BVRE � RECR � G2DR � L2

(2) RequirementsRequirement ‘901’ has been copied from Requirement ‘001’. The Order-related BillingStatus (Header) check has been over-ridden so that 3rd-party Orders can be billed prior tothe Vendor Invoice being posted. Note, the Document Flow Table (VBFA) is checked toensure that the 3rd-party Purchase Requisition has been converted to a Purchase Order.

This Header-level Requirement is used when copying the following Order Types toBilling Types :

OR � F2YBV2 � BV

Requirement ‘912’ has been copied from Requirement ‘012’. The Order-related BillingStatus (Item) check has been over-ridden so that 3rd-party Orders can be billed prior tothe Vendor Invoice being posted. Note, the Document Flow Table (VBFA) is checked toensure that the 3rd-party Purchase Requisition has been converted to a Purchase Order.

This Item-level Requirement is used when copying the following Order Types/ItemCategories to Billing Types :

OR/TAS � F2YBV2/TAS � BV

Billing Blocks

The following Billing Blocks are used :

Materials Management

Configuration Guide

Billing Block Description

01 Calculation Missing

02 Compl Confirm Missing

03 Prices Incomplete

04 Check Terms of Payment

05 Check terms of Delivery

08 Check Credit Memo

09 Check Debit Memo

All of the above can be applied manually in Sales documents.


Consumption Based PlanningFor a full description of MRP refer to the Manufacturing Core Configuration document.This document only covers those elements of MRP specific to Logistics.

Master DataMRP Controllers

One MRP Controller (i.e. ‘001’) is provided for each Plant. This value is automaticallypopulated (and hidden) by the Transaction Variants for the various “Create Material”transactions. Refer Appendix C for further details.

MRP Types

The following MRP Types are used :

MRP Type Description

ND No Planning

P1 MRP Fixing Type 1

PD MRP

VB Manual Reorder Point Planning

Z1 Manual Reorder Point Planning with Requirements

MRP Type ‘Z1’ was copied from ‘VB’ and changed so that the following “externalrequirements” are also taken into account (within the replenishment lead time) :

• Sales Requirements

• Reservations (from Service Orders)

• Delivery schedule for a Stock Transport Order

• Delivery schedule for a Stock Transport Requisition


4.6B R2.00

Only MRP Type ‘Z1’ is intended for use with non-Manufacturing Materials. This valueis automatically populated (and hidden) by the Transaction Variants for the various“Create non-Manufacturing Material” transactions. Refer Appendix C for furtherdetails.

Note, the other MRP Types (e.g. ‘ND’) can be selected via the “Change Material”transaction.

Special Procurement Types

Special Procurement Type ‘99’ has been defined for Plants 0001 – 0010 as follows :

Field Value

Procurement Type F (i.e. External procurement)

Special Procurement K (i.e. Consignment)

This value is set automatically by the Transaction Variant when a consignment materialis created. Refer Appendix C for further details.

Special Procurement Types ‘01’ – ‘10’ have been defined for Plants 1001 – 1050 as follows:

Field Value

Procurement Type F (i.e. External procurement)

Special Procurement U (i.e. Stock Transfer)

Plant 00nn (where nn is the Special Procurement Type)

Special Procurement Types ‘01’ – ‘10’ are used to facilitate replenishment of Plants 1001 –1050 via Stock Transport Orders from Plants 0001 – 0010. For example, if a Material iscreated in Plant 1001 with a Special Procurement Type of ‘04’ then MRP proposals fromPlant 1001 will create requirements on Plant 0004. MRP run on Plant 0004 would thencreate a Stock Transport Requisition to replenish Plant 1001.

PlanningMRP Calculation

(1) Planning HorizonThe Planning Horizon is 100 days in all Plants.

Note, MRP Type ‘Z1’ (i.e. Manual Reorder Point Planning with Requirements) onlyincludes external requirements within the Material’s replenishment lead time.

Lot Size Calculation

The following Lot Size Procedures are used :


Configuration Guide

Lot Size Procedure Description

EX Lot-for-lot order quantity

Lot Size Procedure ‘EX’ is intended for use with non-Manufacturing Materials. Thisvalue is automatically populated (and hidden) by the Transaction Variants for thevarious “Create non-Manufacturing Material” transactions. Refer Appendix C forfurther details.

Storage Location MRP

Storage Location 0005 is not relevant for MRP in all Plants. Therefore any stock in thisStorage Location is not included in an MRP planning run and is not included in a stockavailability check from a Sales Order (unless the Storage Location is entered in the SalesOrder).

No Storage Locations are planned separately.

Procurement Proposals

A new Default Value for Purchasing Operations (‘Y1’) has been created. Among otherthings it controls the conversion of Purchase Requisitions into Purchase Orders. Thefields relevant to procurement proposals are :

Field Value

Reference to Purchase Requisition Items are not automatically pre-selected

Adopt all Display selected items on Overview screen

Adopt all and Save Purchase Order Items are not generated automatically

This default value must be entered in the User Master record as a Parameter ID (usingPID ‘EVO’) for it to be active

PurchasingEnvironment DataDefault Values for Buyers

A new Default Value for Purchasing Operations (‘Y1’) has been created. The keyattributes are :

• Purchasing Information Records are not created automatically from PurchaseOrders.

• Prices are not copied from the last Purchase Order in the event that pricedetermination fails to find a price.

• No automatic source determination in Purchase Requisitions.

This default value must be entered in the User Master record as a Parameter ID (usingPID ‘EVO’) for it to be active


4.6B R2.00

Vendor MasterTerms of Payment

A standard set of Payment Terms has been supplied. These can be changed during eachCustomer Implementation and maintained at any time via the Settings menu option.

Incoterms

The standard SAP Incoterms are supplied unchanged.

Text Types

Both Central Texts and Purchasing Organisation texts have been de-activated via theTransaction Variants for Create, Change and Display Vendor.

Purchasing Groups

Three example Purchasing Groups are supplied although there is no special significancein any of them. These can be changed during each Customer Implementation andmaintained at any time via the Settings menu option.

Purchasing Information Record

(1) Text Types and Copying RulesThe following Text Types are used with Purchasing Information Records :

01 Info Record Note02 Purchase Order Text

Both Text Types are entered manually.

Source List

Source Lists are not mandatory in any Plants.

Purchasing RequisitionDocument Type

The following Purchasing Requisition Document Types are used :

Document Type Description

NB Purchasing Requisition

TP Third-party Requisition

Document Type ‘NB’ has not been changed. Document Type ‘TP’ is an identical copy of‘NB’ that has been created simply to allow easy identification of 3rd-party Requisitions.

Text Types and Copying Rules

The following Text Types are used with Purchasing Requisitions :

01 Item text02 Item Note03 Delivery text04 Material PO text


Configuration Guide

These Text Types are all manually entered or copied from a reference PurchaseRequisition (if exists).

Text Type ‘04’ is also copied from the Material Master (Purchase Order Text).

Purchase OrderDocument Type

The following Purchase Order Document Types are used :

Document Type Description

PO Standard PO

STO Stock Transport Order

The Field Selection Reference Key for Document Type ‘PO’ has been changed from ‘NBF’to ‘ZNBF’ (see below for details). The allowed Item Categories for Document Type ‘PO’are :

StandardK ConsignmentS Third-party

The only allowed Item Category for Document Type ‘STO’ is :

U Stock Transfer

Tolerance Limits for Price Variance

The following Tolerance Keys are defined in Plants 0001 – 0010 :

Tolerance Key Description

PE Price Variance

SE Maximum Cash Discount

When processing a Purchase Order, Tolerance Key ‘PE’ will cause a warning message tobe issued if the effective price is not within –20% or +10% of the Valuation Price in theMaterial Master.

Tolerance Key ‘SE’ will cause a warning message to be issued if a cash discount of morethan 10% of the Valuation Price in the Material Master is given.

Release Procedure

(1) ClassClass ‘PURCHORD’ (Class Type ‘032’) has been created containing the followingstandard SAP Characteristics :

PODOCUMENTTYPE (Document Type)PODGROUP (Purchasing Group)POVALUE (Purchase Order Value)

This allows release conditions to be defined for combinations of Document Type,Purchasing Group and Purchase order Value.


4.6B R2.00

The Class and Characteristics are created by CATT YS_PO_AUTH. Refer Appendix Afor further details.

(2) Release GroupRelease Group ‘01’ has been created (for Purchase Orders) and Class ‘PURCHORD’assigned.

(3) Release CodeThe following Release Codes have been created and assigned to Release Group ‘01’ :

01 Clerk02 Manager03 Budget Manager04 Finance Director05 Managing Director

(4) Release Indicator5 Release Indicators are used to represent the release status of the order.

Release Indicator ‘S’ is used for the initial blocked status.

Release Indicator ‘C’ represents the final cleared status.

Release Indicators ‘1’, ‘2’ & ‘3’ are intermediate status levels between ‘S’ and ‘C’ forRelease Strategies with more than 2 Release Codes.

If a “cleared” Purchase Order is subsequently changed then a new release will berequired if the PO has been output or if a new Release Strategy is required.

(5) Release Strategy5 Release Strategies have been defined for Release Group ‘01’.

No prerequisites.

Release Strategy ‘01’ requires Release Code ‘01’ only.

Release Strategy ‘02’ always requires Release Code ‘02’. Release Code ‘01’ can optionallybe used as an intermediate release but Release Code ‘02’ will still be required.

Release Strategy ‘03’ always requires Release Code ‘03’. Release Codes ‘01’ and ‘02’ canoptionally be used as intermediate releases but Release Code ‘03’ will still be required.

Release Strategy ‘04’ always requires Release Code ‘04’. Release Codes ‘01’, ‘02’ and ‘03’can optionally be used as intermediate releases but Release Code ‘04’ will still berequired.

Release Strategy ‘05’ always requires Release Code ‘05’. Release Codes ‘01’, ‘02’, ‘03’ and‘04’ can optionally be used as intermediate releases but Release Code ‘05’ will still berequired.


Configuration Guide

(6) WorkflowWorkflow has not been activated.

Screen Layout

Field Selection Reference Key ‘ZNBF’ has been created (copied from ‘NBF’) and assignedto Document Type ‘PO’. This FSRK suppresses unwanted fields in the Purchase Order.

Texts

The following Text Types are used with Purchasing Documents at the header level :

01 Header text02 Header note

Both Text Types are manually entered or copied from a reference Purchase Order (ifexists).

The following Text Types are used with Purchasing Documents at the item level :

01 Item text02 Info record PO text

Text Type ‘01’ is copied from the Purchase Requisition Item text.

Text Type ‘02’ is manually entered or copied from a reference Purchase Order (if exists).

Stock Transport Order

(1) PlantThe Sales Area has been set for each of the Supplying Plants (i.e. 0001 – 0010) as follows :

Field Value

Sales Organisation 0001

Distribution Channel 01

Division 01

Therefore, all Stock Transport Orders are processed under this Sales Area in SD.

The Customer Number has been set for each of the Receiving Plants (i.e. 1001 – 1050) toPLANTnnnn (where nnnn is the Plant No.). The Customer Master records are createdduring the software installation via CATT YS_DISTRIBUTION_CUSTOMER. Refer toAppendix A for further details.

(2) Delivery Type/CheckingDelivery Type ‘NL’ (i.e. Replenishment Delivery) is used when creating Deliveries (forall Supplying Plants).

Checking Rule ‘A’ (i.e. SD Order) is used in all Plants.


4.6B R2.00

ConditionsSchema Group

All Purchasing Organisations are assigned to a blank Purchasing Organisation SchemaGroup.

All Vendors are assigned to a blank Vendor Schema Group. Note, The Vendor SchemaGroup field is suppressed on the Vendor Master.

Schema Determination

Calculation Schema ZM0000 is determined for all Purchasing Organisations and allVendors.

Calculation Schema RM2000 is determined for Stock Transport Orders.

Calculation Schema

Calculation Schema ZM0000 was copied from RM0000 and Condition Types that werenot required were removed. No new Condition Types have been added and no otherchanges have been made.

Condition Supplement RM0002 (unchanged) is used with Condition Type PB00. Thisdefines the Conditions that can be entered in Purchasing Information Records.

Calculation Schema RM2000 is the standard schema used with Stock Transport Orders.It has not been changed.

Foreign Trade/Customs

Please refer to the Foreign Trade/Customs chapters in the Sales & Distribution section ofthis document.

Account AssignmentAccount Assignment Category

The following Account Assignment Categories are used :

Account Assignment Category Description

A Asset

F Capital Work In Progress

K Cost Centre/Internal Order

U Unknown

X All auxiliary account assignment

Y Third-Party

The Account Modifier for Account Assignment Category ‘F’ has been changed to ‘ZZZ’.This Account Assignment Category is only meant for use with “Capital Works inProgress”. Purchases for this Account Assignment Category result in postings to aBalance Sheet Account (i.e. Work in Progress). These postings would then be journalledto an asset when the capital job is completed. Refer to the Accounting CoreConfiguration Guide for further details on “Capital Work in Progress”.


Configuration Guide

Account Assignment Category ‘Y’ has been copied from ‘1’. The following changes weremade so that the Sales Order would act as a “Cost Collector” :

• Consumption Posting changed from ‘V’ (i.e. consumption) to ‘E’ (i.e. Sales Order)

• Set Special Stock Indicator to ‘Y’

• Changed Sales Order field from ‘suppressed’ to ‘required’

• Changed G/L Account field from ‘required’ to ‘display’

Item Category / Account Assignment Combinations

All of the above Account Assignment Categories have been assigned to the followingItem Categories :

StandardS Third-PartyU Stock TransferD Service

Statistics

Standard Update Group ‘SAP’ is used by all Item Categories.

Refer also to the Logistics Information Systems chapters in the Logistics General sectionof this document.

MessagesOutput Control

(1) Message TypesThe following Message Type is used :

NEU Purchase Order

The following changes have been made to Output Type ‘NEU’:

• The Communications Strategy has been set to ‘CS01’ so that the output can besent via email if the Vendor Master contains an email address.

• The Output Form has been changed to ZEDRUCK. This Form has been copiedfrom standard Form MEDRUCK so that Customers can customise their outputlayouts.

(2) Message Determination SchemaStandard Message Schema RMBEF1 is assigned to Purchase Orders.

Assign Output Devices to Purchasing Groups

Output Devices can be assigned to Purchasing Groups during each Customerimplementation. This allows Purchase Orders are to be printed not on a single centralprinter but on a different printer for each group of Buyers. Note, Output conditionrecords are still required but they must have a blank Output Device field.

Partner Determination

Partner Schemas are not used.


4.6B R2.00

Inventory Management and Physical InventoryGoods Issue / Transfer PostingsCreate Storage Location Automatically

All plants have been activated for automatic Storage location creation.

The following Movement Types have been activated :

301 – Plant to Plant Transfer302 – Plant to Plant Transfer – Reversal311 – Storage Location transfer within plant312 - Storage Location transfer within plant – Reversal325 – Storage Location transfer within plant – blocked stock326 – Storage Location transfer within plant – blocked stock – Reversal

Allow Negative Stocks.

Negative stocks are only allowed in Plant 0001. This is for Manufacturing use only.

Goods ReceiptsTolerance Limits

The following checks are performed for variances between the Goods Receipt and thePurchase Order :

(1) B1 Order Price Quantity (Error)If the Order Price Quantity is not within –50% or +50% an error message is issued.

(2) B2 Order Price Quantity (Warning)If the Order Price Quantity is not within –20% or +20% a warning message is issued.

(3) VP Moving Average priceThe new Moving Average Price must be within +25% of the old one.

Create Storage Location Automatically

All plants have been activated for automatic Storage location creation.


101 – Goods Receipt for Purchase Order501 – Receipt without Purchase Order505 – Receipt without Purchase Order to blocked stock521 – Receipt without Production Order525 – Receipt without Production Order to blocked stock

Delivery Completed Indicator

The Delivery Completed indicator is set automatically for Goods receipts in

Expiration Date Check

All plants have been activated for Expiry Date / Production Date checking.



Configuration Guide

101 – Goods Receipt for Purchase Order501 – Receipt without Purchase Order505 – Receipt without Purchase Order to blocked stock521 – Receipt without Production Order525 – Receipt without Production Order to blocked stock

Physical InventoryTolerances for Physical Inventory Differences

The following Tolerance Group has been defined in all Company Codes :

£100,000 per document

£10,000 per document item

This Tolerance Group has not been assigned to any users so is inactive.

Cycle Counting

Cycle Counting is allowed in Plant 0001 and is intended for use with Manufacturing.The following Cycle Counting Physical Inventory Indicator can be assigned to Materials:

A 12 counts per yearB 6 counts per yearC 3 counts yearD 1 count per year

The initial parameters for these Indicators are :

CC Indicator Counts/year Float Time (in workdays) Percentage

A 12 5 56

B 6 10 28

C 3 20 14

D 1 0 2

Users can update the above parameters automatically at any time by running the “ABCAnalysis for Cycle Counting” report.

Movement Types

The following Movement Types are used :

101 Goods Receipt for Purchase Order into own stock101/K Goods Receipt for Purchase Order into consignment stock102 Goods Receipt for Purchase Order into own stock – reversal102/K Goods Receipt for Purchase Order into consignment stock – reversal122 Return delivery to vendor from own stock122/K Return delivery to vendor from consignment stock123 Return delivery to vendor from own stock – reversal123/K Return delivery to vendor from consignment stock – reversal501 Receipt without Purchase Order into own stock501/K Receipt without Purchase Order into consignment stock502 Receipt without Purchase Order into own stock – reversal


4.6B R2.00

502/K Receipt without Purchase Order into consignment stock – reversal505 Receipt without Purchase Order into blocked stock506 Receipt without Purchase Order into blocked stock – reversal521 Receipt without Production Order into own stock522 Receipt without Production Order into own stock – reversal525 Receipt without Production Order into blocked stock526 Receipt without Production Order into blocked stock – reversal201 Consumption for cost centre from own stock201/K Consumption for cost centre from consignment stock202 Consumption for cost centre from own stock – reversal202/K Consumption for cost centre from consignment stores – reversal241 Consumption for asset from own stock241/K Consumption for asset from consignment stock242 Consumption for asset from own stock – reversal242/K Consumption for asset from consignment stock – reversal261 Consumption for order from own stock261/K Consumption for order from consignment stock262 Consumption for order from own stock – reversal262/K Consumption for order from consignment stock291 Consumption for all account assignments from own stock291/K Consumption for all account assignments from consignment stock292 Consumption for all account assignments from own stock – reversal292/K Consumption for all account assignments from consignment stock –reversal551 Withdrawal for scrapping from own stock551/K Withdrawal for scrapping from consignment stock552 Withdrawal for scrapping from own stock – reversal552/K Withdrawal for scrapping from consignment stock – reversal555 Withdrawal for scrapping from blocked stock555/K Withdrawal for scrapping from blocked consignment stock556 Withdrawal for scrapping from blocked stock – reversal556/K Withdrawal for scrapping from blocked consignment stock – reversal301 Transfer own stock plant to plant (one-step)302 Transfer own stock plant to plant (one-step)- reversal311 Transfer own stock storage location (one-step)311/K Transfer consignment stock storage location (one-step)312 Transfer own stock storage location (one-step) – reversal312/K Transfer consignment stock storage location (one-step) – reversal325 Transfer blocked stock to blocked stock within plant325/K Transfer blocked consignment to blocked consignment within plant326 Transfer blocked stock to blocked stock within plant – reversal326/K Transfer blocked consignment to blocked consignment within plant –reversal343 Transfer blocked stock to unrestricted stock343/K Transfer blocked consignment to unrestricted consignment344 Transfer blocked stock to unrestricted stock - reversal344/K Transfer blocked consignment to unrestricted consignment – reversal453 Transfer to own stock from customer returns stock454 Transfer to own stock from customer returns stock – reversal459 Transfer customer returns stock to blocked stock460 Transfer customer returns stock to blocked stock – reversal


Configuration Guide

561 Initial entry of own stock balances561/K Initial entry of consignment stock balances562 Initial entry of own stock balances – reversal562/K Initial entry of consignment stock balances – reversal565 Initial entry of blocked stock balances565/K Initial entry of consignment blocked stock balances566 Initial entry of blocked stock balances – reversal566/K Initial entry of consignment blocked stock balances – reversal601 Goods Issue for a customer delivery from own stock601/K Goods Issue for a customer delivery from consignment stock602 Goods Issue for a customer delivery from own stock – reversal602/K Goods Issue for a customer delivery from consignment stock – reversal701 Receipt for own physical inventory stock adjustment701/K Receipt for consignment physical inventory stock adjustment702 Issue for own physical inventory stock adjustment702/K Issue for consignment physical inventory stock adjustment707 Receipt for own blocked physical inventory stock adjustment707/K Receipt for consignment blocked physical inventory stock adjustment707 Issue for own blocked physical inventory stock adjustment707/K Issue for consignment blocked physical inventory stock adjustment

Stock DeterminationStock Determination Strategy

(1) Stock Determination GroupA single Stock Determination Group has been defined in Plants 0001 – 0010. Thepurpose of this Group is to allow stock to be issued (during Shipping) directly fromVendor Consignment stock.

The Stock Determination Group is populated in Consignment Materials via theTransaction Variant for the “Create Consignment Material” transaction. ReferAppendix C for further details.

(2) Stock Determination RuleA single Stock Determination Rule has been defined.

(3) Stock Determination HeaderThe Header (and later the item) table relate to the Stock Determination Strategy(combination of Plant, Group and Rules). Only one strategy applies and therefore allstrategies are setup in the same way.

The sort mechanism used is by Item table and sorted in ascending order. No sorting byprice or quantity has been made and therefore no ranking priority is required.

(4) Stock Determination ItemThe Item table defines the following sequence :


4.6B R2.00

K ConsignmentF Unrestricted

Assign Stock Determination Rule

Stock Determination is only used with Deliveries.

(1) DeliveryStock Determination Rules are assigned to the following Item Categories :

BVN Cash SaleBVNN Cash Sale Free of ChargeTAN Standard ItemTANN Standard Item Free of ChargeTAX Non-stock ItemYTAN Pay & Subsequent Delivery Standard ItemYTNN Pay & Subsequent Delivery Standard Item Free of ChargeYTAX Pay & Subsequent Delivery Non-stock ItemYBOM Standard BoM Sub-itemYBMX Standard BoM Non-stock Sub-itemYBM1 Customer Pick-up BoM Sub-itemYBM2 Customer Pick-up BoM Non-stock Sub-itemYBM3 Pay & Subsequent Delivery BoM Sub-itemYBM4 Pay & Subsequent Delivery BoM Non-stock Sub-item

Valuation and Account AssignmentPrice Control for Material Types

The default Price Control is set to “Standard Price” for all Material Types except ‘YROH’(i.e. Raw Materials) which is set to “Moving Average”.

Account DeterminationValuation Classes

(1) Account Category ReferenceThe following Account Category References are used :


Configuration Guide

Account Category Reference Description

0001 Raw Materials

0005 Trading Goods

0006 Services

0008 Semi-finished Products

0009 Finished Products

(2) Valuation ClassThe following Valuation Classes are used and assigned to Account Category Referencesas shown :

Valuation Class Description Account Category Reference

3000 Raw Materials 0001

3040 Spare Parts 0005

3050 Packaging and Empties 0005

3200 Services 0006

4000 Finished Goods 0005

4010 Stock Account Template 1 0005










7900 Components 0008

7920 Manufactured Materials 0009

(3) Account Category Reference / Material TypeAssigning Account Category References to Material Types provides the user with a listof possible Valuation Classes upon material creation. These Valuation Classes are usedin subsequent account determination.


4.6B R2.00

Material Type Account Category Reference

Z3RD (3rd-Party) 0005

ZMT1 (Standard Stock) 0005

ZMT2 (Non-stock) 0005

ZNVS (No-value Stock) N/A since no Accounting view

ZSER (Service) 0006

YROH (Raw) 0001

YHLB (Component) 0008

YFRT (Manufactured) 0009

YBOM (Sales BoM) 0005

Account Groupings for Movement Types

The Account Grouping for Movement Types ‘291’ and ‘292’ has been changed from‘VBR’ to ‘ZZA’.

Automatic Postings

The automatic posting rules used are :


Configuration Guide

Trans.Key

Description Rule Modifier ValuationClass

G/LAccount

AKO Expense/revenue fromconsignment materialconsumption

ValuationClass

All 500160

AUM Expense/revenue from StockTransfer

Debit /Credit

DR –500410CR -500400

3000 130000

3040 133000

3050 130110

4000 132000

4010 130010

4020 130020

4030 130030

4040 130040

4050 130050

4060 130060

4070 130070

4080 130080

4090 130090

4100 130100

7900 133010

BSX Inventory posting ValuationClass

7920 132010

DIF Material management smalldifferences

500520

FR1 Freight Clearing 208060

FRL External Activity ValuationClass

All 520000

FRN Incidental costs of externalservices

500010

AUF All 500600

BSA All 130900

GBB Offsetting entry for inventoryposting

DR/CR,GeneralModific.,ValuationClass

INV All DR –500510CR -500500


4.6B R2.00

3040 500085

3050 500045

4000 –4100

500025

7900 500105

VAX

7920 500135

3040 500085

3050 500045

4000 –4100

500025

7900 500105

VAY

7920 500135

VBO All 500150

3000 500000

3040 500080

3050 500040

4000 –4100

500020

7900 500100

VBR

7920 500130

3000 500010

3040 500090

3050 500050

4000 –4100

500030

7900 500110

VNG

7920 500140

ZOB All 208040

ZOF All 131000

ZZA All 131000

ZZZ All 114000

KDR MM Exchange Rate RoundingDifferences

DR/CR DR –650040CR –700020

KON Consignment Payables 203090


Configuration Guide

All DR –500210CR -500200

PRA All DR –500210CR -500200

PRD Cost price differences DR/CR,GeneralModific.,ValuationClass

PRF All 500610

UMB Gain/Loss from revaluation DR/CR DR –500310CR -500300

UPF Unplanned Delivery Costs 600000

WRX GR/IR Clearing Account 208030

Invoice VerificationLogistics Invoice VerificationAutomatic Postings

Refer to Automatic Postings in “Valuation and Account Assignment” section above.

Incoming Invoice

(1) Exchange Rate DifferencesExchange rate differences are treated the same as price differences and posted to theprice difference accounts.

(2) Unplanned Delivery CostsUnplanned delivery costs entered in the invoice are distributed among the invoice items.

(3) Vendor Specific TolerancesTolerance Group 0001 has been defined in each Company Code. This Tolerance Groupdoes not perform any invoice tolerance checking. That is, the net invoice amount mustequal the net total of the invoice items. The Tolerance Group is populated in the VendorMaster via the Transaction Variants for the various “create Vendor” transactions. ReferAppendix C for further details.

Invoice Block

(1) Tolerance LimitsThe following checks are performed for variances between the Invoice and PurchaseOrder or Goods Receipt.

(a) BD Form Small Difference Automatically

Logistics Execution

4.6B R2.00

Positive variances for the total invoice within £5 are accepted and an “expense/incomefrom small differences” posting is generated.

(b) KW Variance from Condition Value

Variances between delivery costs and planned delivery costs must be within -£20 or -20% and+£10 or +5%.

(c) PP Price Variance

Invoice item variances must be within -£20 or -20% and +£10 or +2%.

(d) PS Price Variance: Estimated Price

Invoice item variances for estimated prices must be within -£20 or -10% and +£10 or+10%.

(e) VP Moving Average Price Variance

The new Moving Average Price must be within +25% of the old one.

Message Determination

(1) Message TypesThe following Message Type is used for Vendor Consignment Liabilities :

KONS Consignment

(2) Message Determination SchemaStandard Message Schema MR0003 is used for Vendor Consignment Liabilities.

Logistics Execution

ShippingBasic Shipping FunctionsShipping Point and Goods receiving Point Determination

(1) Shipping ConditionsThe following Shipping Conditions are provided :

Logistics Execution

Configuration Guide

Shipping Condition Description

00 <1 Day

01 1 Day

02 2 Days

03 3 Days

04 4 Days

05 5+ Days

(2) Loading GroupsOnly one Loading Group (0001) has been defined. All Customers are assigned to thisLoading Group via the various “Create Customer” Transaction Variants. Refer toAppendix C for further details.

(3) Assign Shipping PointsShipping Points are assigned one-to-one with the Plant for all combinations of ShippingCondition and Loading Group. For example, Shipping Point 1026 will be assigned forPlant 1026.

Scheduling

Delivery Scheduling is activated. Transportation Scheduling is not used.

Determination of Loading Times and Pick/Pack times is de-activated for all ShippingPoints.

Delivery Scheduling consists simply of Transit Times. Refer to the section on Routes foran explanation of Transit Times.

The default Factory Calendar and Working Times specify a Mon-Fri working week from0800 to 1700 (excluding public holidays). This can be changed to a Mon-Sat (excludingpublic holidays), Mon-Sun (excluding public holidays) or 365/366 working days/yearduring implementation.

Routes

(1) Define RoutesThe following Routes are provided :

Logistics Execution

4.6B R2.00

Route Description Transit Time (Days)

Y00 <1 Day 0

Y01 1 Day 1

Y02 2 Days 2

Y03 3 Days 3

Y04 4 Days 4

Y05 5+ Days 5

These cannot be changed.

(2) Route Determination

(a) Transportation Zones

Only one Transportation Zone (0000000001) has been created for Country GB. Therefore,all delivering Shipping Points reside within this Transportation Zone.

A single Transportation Zone (0000000001) has also been defined for every otherCountry in the system.

All Customers are assigned to Transportation Zone ‘0000000001’ regardless of Countryvia the various “Create Customer” Transaction Variants. Refer to Appendix C forfurther details.

(b) Transportation Groups

Only one Transportation Group (0001) has been defined. All Customers are assigned tothis Transportation Group via the various “Create Customer” Transaction Variants.Refer to Appendix C for further details.

(c) Route Determination

Route determination is defined (without Weight Groups) from Departure Country GB toall Destination Countries (including GB) as follows :

Shipping Condition Transportation Group Proposed Route

00 (i.e. < 1 Day) 0001 Y00 (i.e. < 1 Day)

01 (i.e. 1 Day) 0001 Y01 (i.e. 1 Day)

02 (i.e. 2 Days) 0001 Y02 (i.e. 2 Days)

03 (i.e. 3 Days) 0001 Y03 (i.e. 3 Days)

04 (i.e. 4 Days) 0001 Y04 (i.e. 4 Days)

05 (i.e. 5+ Days) 0001 Y05 (i.e. 5+ Days)

Therefore, it can be seen that the only factor that affects the Route (and therefore theDelivery Schedule lead times) is the Shipping Condition from the Customer Master.

Logistics Execution

Configuration Guide

Output Control

(1) Output Determination

(a) Outbound Deliveries

(i) Output Types

The following Delivery Output Type is used :

LD00 Delivery Note

The following changes have been made to LD00 :


• The Output Program has been changed to YS_RVADDN01. This program issimply a copy of RVADDN01.

• The Output Form has been changed to ZVDELNOTE. This Form is simply acopy of standard Form RVDELNOTE_SUPPL so that Customers can customisetheir Delivery Note layout. The associated Output Program (RVADDN01) hasalso been copied to keep the Output Program and Form consistent.

(ii) Output Determination Procedure

The following Output Procedure is used with Deliveries :


V10000 (Delivery Header Output) LD00 (Delivery Note)

This procedure is assigned to the following Delivery Types :

Billing Document Type Output Procedure

LF (Outbound Delivery) V10000

LR (Returns Delivery) V10000

YBV (Pay & Subsequent Delivery) V10000

(b) Picking

(i) Output Types

Output Types EK00 is used for Picking Lists.

The associated Output Form has been changed to ZVPICKSIN. This Form is simply acopy of standard Form RVPICKSIN so that Customers can customise their Picking Notelayout.

EK00 has been assigned to all Shipping Points.

Logistics Execution

4.6B R2.00

DeliveriesDelivery Types

The following Delivery Types are used :

Delivery Type Description

BV Cash Sale

NL Replenishment Delivery

LF Standard Delivery

LR Returns delivery

YBV Pay & Subsequent Delivery

Delivery Type NL is used for Stock Transport Orders.

Delivery Types BV, LF, LR and YBV are used for Order Types BV, OR, RE and YBV2respectively.

Item Categories

Delivery Item categories are simply copied from the corresponding Sales Order ItemCategories except in the case where a new Delivery Item is determined (i.e. there is nosource Sales Order Item Category). This is true for :

• Batch Splits (i.e. usage ‘CHSP’) :

Delivery Type Item Category Group Usage Higher Level Item Cat. Item Category

BV NORM CHSP BVN

BV NORM CHSP BVNN BVNN

BV NORM CHSP YBM1 YBM1

NL NORM CHSP NLN

LF NORM CHSP TAN

LF NORM CHSP TANN TANN

LF NORM CHSP YBOM YBOM

LR NORM CHSP REN

YBV NORM CHSP TAN

YBV NORM CHSP YTNN YTNN

YBV NORM CHSP YBM3 YBM3

• Replenishment Deliveries resulting from Stock Transport Orders (i.e. Usage ‘V’) :

Logistics Execution

Configuration Guide

Delivery Type Item Category Group Usage Higher Level Item Cat. Item Category

NL NORM V NLN

• Items added manually in the Delivery.

Delivery Type Item Category Group Usage Higher Level Item cat. Item Category

LF NORM DLN

NL NORM ULN

LR NORM REN

Delivery Blocks

The following Delivery Blocks are used :

Delivery Block Description

01 Credit Limit

06 No Printing

Z1 Not to be delivered

Delivery Block ‘01’ blocks Picking and Goods Issue. It does not block creation ofDeliveries. This Delivery Block should not be confused with the Credit Blockautomatically applied by Credit Management “Automatic Credit Control”. It is amanual block that can be used to stop goods physically leaving the warehouse.

Delivery Block ‘06’ blocks printing of the Order Confirmation.

Delivery Block ‘Z1’ blocks creation of Deliveries. Note, this is effected via Copy Control(see below) rather than standard configuration because the standard “delivery blocking”only blocks creation via the Delivery Due List. Copy Control blocks all methods (e.g.“Sales Document � Deliver” from within the Sales Order).

Copying ControlCopy Control

Copy Control has been defined for the following Order Types to Delivery Types :

OR � LFBV � BVYBV2 � YBVRE � LRDL � NL

Requirements

Requirement ‘901’ has been copied from Requirement ‘001’ and a check included toprevent the creation of a Delivery if Delivery Block ‘Z1’ exists in the Sales Order Header.

This Requirement is used when copying the following Order Types to Delivery Types :

Logistics Execution

4.6B R2.00

OR � LFBV � BVYBV2 � YBV

PickingDetermine Picking Location

(1) RuleAll Delivery Types use standard rule ‘MALA’ to automatically determine the PickingLocation during creation of Deliveries.

Rule ‘MALA’ determines the Picking Location based on the Shipping Point, Plant andStorage Condition.

(2) Storage ConditionsThe following Storage Conditions are provided :

Storage Condition Description

01 To Storage Location 0001










(3) Assign Picking LocationsIn Plants 0001 – 0010 the Storage Locations are assigned as follows (where nnnn is thePlant number) :

Logistics Execution

Configuration Guide

Shipping Point Plant Storage Condition Storage Location

nnnn nnnn 01 0001

nnnn nnnn 02 0002

nnnn nnnn 03 0003

nnnn nnnn 04 0004

nnnn nnnn 05 0005

nnnn nnnn 06 0006

nnnn nnnn 07 0007

nnnn nnnn 08 0008

nnnn nnnn 09 0009

nnnn nnnn 10 0010

In Plants 1001 – 1050, 2000, 3000, 4000 & 5000 the Storage Locations are assigned asfollows (where nnnn is the Plant number) :

Shipping Point Plant Storage Condition Storage Location

nnnn nnnn 01 0001

nnnn nnnn 02 0002

nnnn nnnn 03 0003

nnnn nnnn 04 0004

nnnn nnnn 05 0005

WorklistsList Profile

A new List Profile (Z003) has been created for use with the Delivery Due List. Thisprofile was copied from standard Profile 0003 and the following changes made :

• List Display changed from “index list” to “document list”.

• Name of Ship-to Party is displayed in list.

• Default selection rule changed from “all deliveries due today and tomorrow” to“all deliveries due up to tomorrow”.

• Maximum delivery selection date changed from 30 days in future to 60 days.

Assignment of List Profiles to Scenarios

The “default scenario for transaction VL10” has been defined as follows :

Logistics Execution

4.6B R2.00

Field Value

Profile Z003

Selection Screen User Exit Z

The User Exit (defined in LV50R_PREFZ1) specifies that the Delivery Due List should berun using Report Variant YS_DELIV (for program RVV50R10A). This Variant hidesunwanted fields in the initial selection screen.

Refer to Appendix B for further details of the User Exit.

Appendix A - Delivered Master Data

Configuration Guide


Customers Master DataPlant to plant stock transfers require a “dummy” Customer for each of the receivingPlants. There are 50 possible receiving plants in Company Code 0001. Therefore, 50Customer Master records are provided.

The Customers are numbered PLANT1001 – PLANT1050 and are assigned to Plants 1001– 1050 respectively. These Customers are created by CATTYS_DISTRIBUTION_CUSTOMER during the installation process.

Tax RecordsCondition records (Condition Type MWST) for UK domestic tax rates are provided tominimise the effort required to implement each customer.

These condition records are created by CATT YS_TAX_RECORDS. Note. this CATTdoes not create any export sales tax condition records. These must be created manuallyduring the implementation of each Customer.

Batch Determination ClassBatch Managed Materials use the Classification system for the automatic determinationof batches during delivery processing. Selection Class Y_FIFO (Class Type ‘022’) isprovided with the following Characteristics:

• LOBM_VFDAT Expiration date, shelf life

• Y_BIN Storage Bin

LOBM_VFDAT is a standard Characteristics. Y_BIN has been included so that a BinLocation can be maintained for each batch.

Sort Sequence Y_FIFO is created with the LOBM_VFDAT Characteristics defined as theascending sort key.

The Selection Class, Sort Sequence and Characteristics are created by CATTYS_BATCH_MGT.

Purchase Order Release Strategy ClassPurchase Orders use the Classification system for Release processing (i.e. authorisation).Class PURCHORD (Class Type ‘032’) is provided with the following standardCharacteristics:

• PODOCUMENTTYPE Purchase Order Type


4.6B R2.00

• PODGROUP Purchasing Group

• POVALUE Total net order value

The Class and Characteristics are created by CATT YS_PO_AUTH.

Appendix B - User Exits

Configuration Guide


Extending Material Master using Create transaction

Project: SERVICE

Enhancement: MGA00001

Component: EXIT_SAPLMGMU_001

Description: When extending a Material into a new Plant it ispossible to extend the Material using a differenttransaction from that originally used to create theMaterial. If this happens it is possible that theTransaction Variant of the new transaction will resethidden values set by the Transaction Variant when theMaterial was first created.

EXIT_SAPLMGMU_001 ensures that Materials areonly extended using the same transaction they wereoriginally created with.

Authorisation to delete Deliveries

Program: MV50AFZ1

Form: USEREXIT_SAVE_DOCUMENT_PREPARE

Description: Within standard R/3, Users who are authorised tochange Deliveries are also allowed to delete Deliveries.A new Authorisation Object has been created in SME(YS_LO_DELDELETE) to control access to the deletefunction.

USEREXIT_SAVE_DOCUMENT_PREPARE checksthat the user has been assigned this new ActivityGroup whenever they attempt to delete a Delivery.An error message is issued if they do not have theappropriate permission.

Note, Deliveries can only be deleted by users withactivity group ‘YS_LO_DELDELETE’ assigned.


4.6B R2.00

Source Plant determination in Sales Order

Program: MV45AFZB

Form: USEREXIT_SOURCE_DETERMINATION

Description: Within standard R/3 the Source Plant used forDeliveries is determined by a logic sequence asfollows.

1. Customer/Material Information Record

2. Customer Master (ship to)

3. Material Master

The Source Plant defaults from the Customer/MaterialInformation Record then Customer Master (ship todestination) and finally Material Master.

USEREXIT_SOURCE_DETERMINATION adds afourth level of default, which defines the source if noother source has been defined. The source is definedas that specified in parameter ID ‘WRK’ from the UserMaster Record of the logged on user.

Create Deliveries Report Variants

Program: LV50R_PREFZ1

Form: SEL_SCREEN_USER

Description: This user exit specifies the Report Variant (YS_DELIV)that is used when the Delivery Due List is executed.

Report Variant YS_DELIV suppresses fields that arenot required.

Profit Centre Substitution

Program: YGGBS000

Form: GET_EXIT_TITLES & Y901


Configuration Guide

Description: In standard SAP the Profit Centre (to receive the salesrevenue) is determined from the Material Master(Sales Data 2 view) using the Delivering Plant. That is,each combination of Material/Plant has a pre-definedProfit Centre. The Profit Centre can be manuallyentered or changed during Sales Order entry.

An alternative method for determining Profit Centreshas been provided using a Profit Centre “SubstitutionRule” (Y901). This method uses the Plant from theuser’s Parameter ID (if present) to determine the ProfitCentre regardless of the delivering Plant. Thus, eachuser can effectively have a default Profit Centre thatwill override the Profit Centre determined via thedelivering Plant. For users without a Plant ParameterID the normal rule will apply.

If required, this alternative rule must be activated viathe menu option provided on the LogisticsImplementor menu.

Eligibility of Invoice Line Items for Intrastat reporting

Program: RVEXKUEI

Description: When generating Intrastat report within standard R/3the selection of Invoice Line Items is restricted to apredetermined list of item categories.

RVEXKUEI amends this list to include the extra LineItems shown in the following categories:

Customer Pick-up:– Stock Item– Free Stock Item– Non-Stock Item

Pay & Subsequent Delivery :– Stock Item– Non-Stock Item

Return:– Free Item

Appendix C - Transaction Variants

4.6B R2.00


Transaction Variants are used extensively throughout Logistics, in the most part simplyto suppress unwanted fields or to de-activate menu options. The Transaction Variantsdocumented below are more critical in that they also populate some fields with data.

Create Purchase Requisition (ME51)Transaction ME51 has a Standard Variant YS_ME51_001. This Variant sets the value ofDocument Type to ‘NB’ (i.e. Purchase Requisition).

Create Consignment Purchase Order (YPOCNS)Transaction YPOCNS calls Transaction ME21 with Transaction Variant YS_ME21_001.

This Variant sets the following values :

Order Type: PO (i.e. Standard Purchase Order)Item Category: K (i.e. Consignment)

Total Material Planning (MD01)Transaction MD01 has a Standard Variant YS_MD01_001.


Processing Key: NETCH (i.e. Net change planning run)Create Purchase Req.: 2 (i.e. Create Purchase Requisitions)Schedule Lines: 3Create MRP List: 1 (i.e. Create MRP List)Planning Mode: 1Scheduling: 1

Individual Material Planning (MD03)Transaction MD03 has a Standard Variant YS_MD03_001.


Processing Key: NETCH (i.e. Net change planning run)Create Purchase Req.: 2 (i.e. Create Purchase Requisitions)Schedule Lines: 3Create MRP List: 1 (i.e. Create MRP List)Planning Mode: 1Scheduling: 1

Create Stock Transport Order (ME27)Transaction ME27 has a Standard Variant YS_ME27_001. This Variant sets the value ofOrder Type to ‘STO’ (i.e. Stock Transport Order).

Create Inquiry (VA11)Transaction VA11 has a client-independent Standard Variant YS_VA11_001. The Variantis client-independent because Variants for Sales Documents must be assigned to the


Configuration Guide

relevant Order Type via the IMG and this assignment only allows for client-independentVariants.


Order Type: IN (i.e. Inquiry)Division: 01 (i.e. General Products)

Create Quotation (VA21)Transaction VA21 has a client-independent Standard Variant YS_VA21_001. The Variantis client-independent because Variants for Sales Documents must be assigned to therelevant Order Type via the IMG and this assignment only allows for client-independentVariants.


Order Type: QT (i.e. Quotation)Division: 01 (i.e. General Products)

Create Sales Order (VA01)Transaction VA01 has client-independent Standard Variants YS_VA01_001,YS_VA01_002, YS_VA01_003 & YS_VA01_004. These Variants are client-independentbecause Variants for Sales Documents must be assigned to the relevant Order Type viathe IMG and this assignment only allows for client-independent Variants.

Transaction Z422 calls Transaction VA01 with Variant YS_VA01_001 which sets thefollowing values :

Order Type: OR (i.e. Standard Order)Division: 01 (i.e. General Products)

Transaction Y031 calls Transaction VA01 with Variant YS_VA01_005 which sets thefollowing values :

Order Type: BV (i.e. Customer Pick-up)Division: 01 (i.e. General Products)

Transaction Y033 calls Transaction VA01 with Variant YS_VA01_006 which sets thefollowing values :

Order Type: YBV2 (i.e. Pay & Subsequent Delivery)Division: 01 (i.e. General Products)


Order Type: RE (i.e. Return Order)Division: 01 (i.e. General Products)


Order Type: CR (i.e. Credit Note)Division: 01 (i.e. General Products)



4.6B R2.00

Order Type: DR (i.e. Debit Note)Division: 01 (i.e. General Products)

Create Pro-Forma Invoice (Y_SED_43000046)Transaction Y_SED_43000046 calls Transaction VF01 with Transaction VariantYS_VF01_001. This Variant sets the value of Billing Type to ‘F5’ (i.e. order-related Pro-forma invoice).

Sales Planning (KEPM)Transaction KEPM has a Standard Variant YS_KEPM_001. This Variant sets the value ofOperating Concern to ‘0001’.

Sales Profitability Analysis (Y035)Transaction Y035 calls Transaction KE30 with Transaction Variant YS_KE30_001.


Operating Concern: 0001Report: SALEANALYSIS

Plan V’s Actual Report (Y036)Transaction Y035 calls Transaction KE30 with Transaction Variant YS_KE30_002.


Operating Concern: 0001Report: PLAN-ACTUAL

Customer Contribution Report (Z420)Transaction Z420 calls Transaction MCSG with Transaction Variant YS_MCSG_001.


Evaluation Structure: S001 (i.e. Standard Customer Info. Structure)Evaluation: Z001 (i.e. Customer Contribution Report)

Material Contribution Report (Z421)Transaction Z421 calls Transaction MCSG with Transaction Variant YS_MCSG_002.


Evaluation Structure: S001 (i.e. Standard Customer Info. Structure)Evaluation: Z002 (i.e. Material Contribution Report)

Create Stock Material (YS_MM01_ZMT1)Transaction YS_MM01_ZMT1 has a Standard Variant YS_MM01_ZMT1_001.


Industry Sector: G (i.e. General)Material Type: ZMT1 (i.e. Stock Material)General Item Cat. Group: NORM (i.e. Standard Item)Material Statistics Group: 1 (i.e. Standard Material)


Configuration Guide

Item Category Group: NORM (i.e. Standard Item)Transport Group: 0001 (i.e. Normal)Loading Group: 0001 (i.e. Normal)Availability Check: 02 (i.e. Individual Requirements)MRP Type: Z1 (i.e. Re-order point planning)MRP Controller: 001Lot Size: EX (i.e. Lot-for-lot order quantity)

Create Non-Stock Material (YS_MM01_ZMT2)Transaction YS_MM01_ZMT2 has a Standard Variant YS_MM01_ZMT2_001.


Industry Sector: GMaterial Type: ZMT2 (i.e. Non-stock Material)General Item Cat. Group: NLAG (i.e. Non-stock Material)Material Statistics Group: 1Item Category Group: NLAG (i.e. Non-stock Material)Transport Group: 0001Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create No Value Stock Material (YS_MM01_ZNVS)Transaction YS_MM01_ZNVS has a Standard Variant YS_MM01_ZNVS_001.


Industry Sector: GMaterial Type: ZNVS (i.e. No-value Stock Material)General Item Cat. Group: NORM (i.e. Standard Item)Material Statistics Group: 1Item Category Group: NORM (i.e. Standard Item)Transport Group: 0001Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create Service Material (YS_MM01_ZSER)Transaction YS_MM01_ZSER has a Standard Variant YS_MM01_ZSER_001.


Industry Sector: GMaterial Type: ZSER (i.e. Service Material)General Item Cat. Group: LEIS (i.e. Service without delivery)Material Statistics Group: 1Item Category Group: LEIS (i.e. Service without delivery)Transport Group: 0001


4.6B R2.00

Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create Third-Party Material (YS_MM01_Z3RD)Transaction YS_MM01_Z3RD has a Standard Variant YS_MM01_Z3RD_001.


Industry Sector: GMaterial Type: Z3RD (i.e. 3rd-party Material)General Item Cat. Group: BANS (i.e. 3rd-party item)Material Statistics Group: 1Item Category Group: BANS (i.e. 3rd-party item)Transport Group: 0001Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create Consignment Material (YS_MM01_CONS)Transaction YS_MM01_CONS has a Standard Variant YS_MM01_CONS_001.


Industry Sector: GMaterial Type: ZMT1 (i.e. Stock Material)Special Procurement Key: 99 (i.e. Vendor Consignment)Stock Determination Group: 0001 (i.e. Standard)General Item Cat. Group: NORM (i.e. Stock Material)Material Statistics Group: 1Item Category Group: NORM (i.e. Stock Material)Transport Group: 0001Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create Sales BoM Header (YS_MM01_SBOM)Transaction YS_MM01_SBOM has a Standard Variant YS_MM01_SBOM_001.


Industry Sector: GMaterial Type: YBOM (i.e. Sales BoM Header)General Item Cat. Group: YBOM (i.e. Sales BoM Header)Material Statistics Group: 1Item Category Group: YBOM (i.e. Sales BoM Header)Transport Group: 0001


Configuration Guide

Loading Group: 0001Availability Check: 02MRP Type: Z1MRP Controller: 001Lot Size: EX

Create Competitive Product (MMW1)Transaction MMW1 has a Standard Variant YS_MMW1_001. This Variant sets the valueof Industry Sector to ‘G’ (i.e. General).

Create Alternative Product Code (VB11)Transaction VB11 has a Standard Variant YS_VB11_001.


Material Determ. Type: A001 (i.e. Based on Material entered)Proposed Reason: Z001 (i.e. Alternative Product Code)

Create Sales BoM (Y_SED_43000135)Transaction Y_SED_43000135 calls Transaction Cs01 with Transaction VariantYS_CS01_002. This Variant sets the value of Usage to ‘5’ (i.e. Sales).

Create Sold-to Party (Z0001)Transaction Z0001 calls Transaction XD01 with Transaction Variant YS_XD01_001.


Country: GB (i.e. United Kingdom)Transportation Zone: 0000000001 (i.e. United Kingdom)Account Group: 0001 (i.e. Sold-to Party)Customer Pricing Procedure: 1 (i.e. Standard)Customer Statistics Group: 1 (i.e. Standard Customer)

Create Ship-to Party (Z0002)Transaction Z0002 calls Transaction XD01 with Transaction Variant YS_XD01_002.


Country: GBTransportation Zone: 0000000001Account Group: 0002 (i.e. Ship-to Party)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Payer (Z0003)Transaction Z0003 calls Transaction XD01 with Transaction Variant YS_XD01_003.


Country: GBTransportation Zone: 0000000001Account Group: 0003 (i.e. Payer)


4.6B R2.00

Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Bill-to Party (Z0004)Transaction Z0004 calls Transaction XD01 with Transaction Variant YS_XD01_004.


Country: GBTransportation Zone: 0000000001Account Group: 0004 (i.e. Bill-to Party)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Sold-to Party – Manual Number (ZZ001)Transaction ZZ001 calls Transaction XD01 with Transaction Variant YS_XD01_007.


Country: GBTransportation Zone: 0000000001Account Group: Z001 (i.e. Sold-to Party – Manual Number)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Ship-to Party – Manual Number (ZZ002)Transaction ZZ002 calls Transaction XD01 with Transaction Variant YS_XD01_008.


Country: GBTransportation Zone: 0000000001Account Group: Z002 (i.e. Ship-to Pary – Manual Number)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Payer – Manual Number (ZZ003)Transaction ZZ003 calls Transaction XD01 with Transaction Variant YS_XD01_009.


Country: GBTransportation Zone: 0000000001Account Group: Z003 (i.e. Payer – Manual Number)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Bill-to Party – Manual Number (ZZ004)Transaction ZZ004 calls Transaction XD01 with Transaction Variant YS_XD01_010.


Country: GBTransportation Zone: 0000000001


Configuration Guide

Account Group: Z004 (i.e. Bill-to Party – Manual Number)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create One-Time Customer (Y030)Transaction Y030 calls Transaction XD01 with Transaction Variant YS_XD01_006.


Country: GBAccount Group: CPDA (i.e. One-Time Customer)Customer Pricing Procedure: 1Customer Statistics Group: 1

Create Prospect (Z0005)Transaction Z0005 calls Transaction XD01 with Transaction Variant YS_XD01_005.


Country: GBTransportation Zone: 0000000001Account Group: 0005 (i.e. Prospect)Customer Pricing Procedure: 1Customer Statistics Group: 1

Convert Prospect to Customer (XD07)Transaction XD07 has a Standard Variant YS_XD07_001.


Country: GBTransportation Zone: 0000000001Customer Pricing Procedure: 1Customer Statistics Group: 1New Account Group: 0001 (i.e. Sold-to Party)

Create Competitor (Z0006)Transaction Z0006 calls Transaction VD01 with Transaction Variant YS_VD01_001.


Country: GBAccount Group: 0006 (i.e. Competitor)

Create Vendor (XK01)Transaction XK01 has a Standard Variant YS_XK01_001.


Account Group: VEND (i.e. Vendor)Tolerance Group: 0001 (i.e. Standard)Country: GB (i.e. United Kingdom)


4.6B R2.00

Create Vendor – Manual Number (YXK01_1)Transaction YXK01_1 calls Transaction XK01 with Transaction Variant YS_XK01_002.


Account Group: ZVND (i.e. Vendor – Manual Number)Tolerance Group: 0001Country: GBOrder Currency: GBP

Create Employee (YXK01_2)Transaction YXK01_2 calls Transaction XK01 with Transaction Variant YS_XK01_003.


Account Group: YEMP (i.e. Employee)Country: GB

Create One-Time Vendor (YXK01_3)Transaction YXK01_3 calls Transaction XK01 with Transaction Variant YS_XK01_004.


Account Group: ONE (i.e. One-time Vendor)Tolerance Group: 0001Country: GBOrder Currency: GBP

Appendix D - Activity Groups

Configuration Guide


YS_LO_CUSTSERREP (Customer Services Representative)This Activity Group allows a Customer Services Representative to enter CustomerOrders, create the resultant Invoices and produce all sales-related reports. The ActivityGroup also allows maintenance of the Master Data require to support these processes(e.g. Customers, Prices, Discounts etc.).

YS_LO_SDCLERK (Delivery Clerk)This Activity Group allows a Delivery Clerk to enter Goods Receipts, issue stock, createdeliveries and produce all related reports. It does not allow users to delete deliveries.

YS_LO_DELDELETE (Delivery Deletion)This Activity Group allows a user to delete deliveries. Users are not given the authorityto delete a delivery in Activity Group YS_LO_SDCLERK.

YS_LO_PAADMIN (Profitability Analysis Administrator)This Activity Group allows a user to post miscellaneous adjustments directly toProfitability Analysis. It would normally only be used to correct erroneous postings butcould also be used to post transactions that have taken place that do not appear inProfitability Analysis (e.g. Finance-only Invoices).

YS_LO_PURCHCLERK (Purchasing Clerk)This Activity Group allows a Purchasing Clerk to enter Purchase Requisitions, PurchaseOrders and produce all purchase-related reports. The Activity Group also allowsmaintenance of the Master Data required to support these processes (e.g. Materials,Vendors, Source List, Purchasing Info. records etc.).

YS_LO_POCLERK (Purchase Order Release – Clerk)This Activity Group allows usage of Release Code ‘01’ when approving PurchaseOrders.

It must be used in conjunction with Activity Group YS_LO_PURCHCLERK.

YS_LO_POMANAGER (Purchase Order Release – Manager)This Activity Group allows usage of Release Code ‘02’ when approving PurchaseOrders.


YS_LO_BUDGETMGR (Purchase Order Release – Budget Manager)This Activity Group allows usage of Release Code ‘03’ when approving PurchaseOrders.



4.6B R2.00

YS_LO_FINANCEDIR (Purchase Order Release – Finance Director)This Activity Group allows usage of Release Code ‘04’ when approving PurchaseOrders.


YS_LO_MANDIR (Purchase Order Release – Managing Director)This Activity Group allows usage of Release Code ‘05’ when approving PurchaseOrders.


YS_LO_STATREP (Statutory Reporting)This Activity Group allows a user to run the statutory reports that are associated withthe Logistics processes (i.e. Intrastat). All reports and data preparation steps required toproduce Intrastat reports are included in this Activity Group

YS_LO_STOCKCLERK (Stock Clerk)This Activity Group allows a Stock Clerk to enter all stock issues, receipts & transfers,enter Purchase Orders and perform periodic stock-takes. All stock analysis reports arealso included within this Activity Group.

YS_LO_STOCKPLNR (Stock Planner)This Activity Group allows a Stock Planner to perform material planning (i.e. MRP) andto close stock periods each month. The Activity Group also allows creation of MaterialMaster data for non-Manufacturing Materials.

YS_LO_CCSTOCKCONTROLLER (Cycle Counting Analysis &Approve)

This Activity Group allows a Stock Clerk to perform ABC Analysis for Cycle Counting,create Physical Inventory Documents and post differences.

YS_LO_CCSTOCKCLERK (Cycle Counting Results Entry)This Activity Group allows a Stock Clerk to enter the results of a Cycle CountingInventory Count.

YS_LO_CCSTOCKDISPLAY (Cycle Counting Display Only)This Activity Group allows a user to simply display Physical Inventory Documents andthe results of a Cycle Counting Inventory Count.

YS_LO_IMPLEMENTOR (Implementor)This Activity Group provides access to all of the implementation transactions used bythe ASP when configuring Logistics.