Help with the Help - Gottipati Blog · Help with the Help Lawrence Matusek, eLogic Rick Servello, ... BOM explosion numbers are explained in the help, ... • MRP generates requirements

Help with the Help

Lawrence Matusek, eLogic

Rick Servello, eLogic

Rama Gottipati, eLogic

Dave Keck, eLogic

CWG 2016

© 2016 eLogic l All Rights Reserved l Proprietary and Confidential

OUR SOLUTIONSOUR COMPANY OUR MARKETS

© 2016 eLogic l Proprietary & Confidential. All Rights Reserved.

17 years of proven excellence in Commerce & Customer Engagement Solutions for Manufacturers.


Some Representative Customers

SAP Help Covers Most VC Topics


…but you might not know where to look or what it means.

Presentation Goals:

Identify relevant topics you won’t find under VC

Explain what some Help points are really trying to say

Point out gaps in the Help

Dates and ECM


Configuration Date


• In Sales, the Configuration Date is based on Material Availability Date by Default (but there is a User Exit) and stored in VBAP-STDAT

• Changes to MAD will prompt (but not force) you to reconfigure• The Configuration Date cannot be directly changed like Pricing Date• For Low Level Configuration (i.e. BOM and routing explosion), the

Configuration Date typically depends on MRP settings

Since you cannot directly edit VBAP-STDAT in a sales document, BOM Explosion Numbers provide a way to make ad hoc changes to an item’s configuration date

Configuration data and dependency effectivity is based on the “Configuration Date”, but how is that date determined?

BOM Explosion Numbers

BOM explosion numbers are explained in the help, but not in the context of variant configuration


Change Standard Order 14463: Overview

• BOM explosion number will ensure that the BOM structure is always exploded with the same date• Can be assigned to a planned order or to sales order item in a make to order scenario

Once ECM, Always ECM (or not?)

Most VC objects that are changed with ECM must thereafter be changed with ECM

Except for BOMs which offer an authorization to bypass the ECM requirement


Display Characteristic Change Characteristic

Remember that you can Undo ECM!

Well, if you act quickly enough…

Transaction: CCUNDO

Authorization: C_AENR_BGR

BADI: ECM_UNDO. Additional logic can be added to BADI for objects not supported by CC_UNDO

Make sure to undo the changes in the right sequence

This functionality was added due to the influence of the CWG!


As useful as this is, you should understand the Help; there are caveats.

For Example: If you set ECM on an object for

the first time, it must be maintained with ECM

thereafter (even though you used Undo)

Material Variants


Variant Matching in Sales Documents

Variant matching is subject to several restrictions

1. Behavior is controlled by sales item category settings

2. Cannot match on sales subitems (but possible workaround)

3. Cannot match multi-level material variants (i.e. root only)

4. Only plant specific configurations are matched

5. Characteristic matching exclusions are processed

6. Partial matches are not considered in sales


Multiple matches are possible (especially when exclusions are

used) and if they occur then processing is

subject to item category settings.

Variant Matching Exclusions

There are more exclusion options than you may realize…

Click the “i” button in selection screen for additional details


Characteristic exclusions can be made for specific

materials (using the selection screen) and

specific plants (using the last toolbar button)

Reference characteristics exclusions can be toggled on and off using the “+”

and “-” buttons respectively

Tip: check the Serial No. and Exclusion Types

together

Migrating Characteristic Exclusions

1. Manually is the only known option short of a custom utility

2. Cannot create a transport for this data due to internal object number for characteristic


How do you migrate variant matching exclusions from system to system?

Configure a Material Variant

Configuring a Material Variant – You can if the corresponding requirements class related to item category permits/requires. It then becomes an individual requirement

Variant Match – You can if the item category permits it

You can even variant match again and find another variant of that KMAT


Sales BOM for a Material Variant

This seems like a contrary use case, but it is technically feasible

You need the structural scope “D” in the item category and a (configurable) sales relevant BOM


This approach can be used for storing

configurable kits or bundles under a static

material number.

Multi-Level Material Variants

Can be implemented with enhancement CCUXMVAR

But matching only considers the root instance


Be careful when you have configurable

materials (with instances) subordinate

to a material variant because you will need

independent requirements to distinguish the

valuation

Material Variants in Class Nodes

You can match material variants in class nodes using enhancement CCUXOBTY

This eliminates the need for separate type 300 classification of these materials


Material Variant Recursion

• Error message “Material is Recursive” occurs if the low level code of the material variant is determined to be lower than its parent

• Implement SAP Note 1833611 if required to determine the correct low level code based on the BOM structure during MRP and costing


Replacing class items with material variants may result in costing or MRP errors

Material Variant BOM Linking

• If you have material variant locking issues after save, recursion checking may be the cause

• Recursion checking time increases exponentially with the number of variants for a configurable material (1000+ variants becomes a concern)


Low Level Code is calculated on BOM save and linking a material variant to a configurable BOM (transaction CS40)

Order BOMs


ConfigurableSeparates interactive configuration between sales and production. Supports SOLI specific adaptation of production BOM structure with the addition and deletion of configurable and non-configurable items.

• Order BOM created from Material BOM explosion• Edit all SOLI Order BOM assemblies collectively• Subassembly cstic value assignments in CU51 • Instantiation is possible (or required) in CU51• Reconfiguration updates non-edited BOM items

Non-ConfigurableProvides a SOLI specific, static structure that effectively overrides a material BOM explosion.

• Order BOM created manually or programmatically• Edit each Order BOM assembly individually• All cstic value assignments in sales document• Instantiation is NOT supported• Reconfiguration has no effect (i.e. static structure)

CS61/2CU51

Configurable and Non-Configurable


Order BOM Merge


This is from the PP help and explains the

process well

Many are not familiar with this aspect of

order BOMs

The merge can be prevented by user exit

How deep does CU51 go?

In CU51, you can edit non-configurable order BOMs

(below configurable ones) and limit the depth of the

explosion for performance or clarity (ad hoc)

Yes, but only if you uncheck the setting for the

Configurable Assemblies Only checkbox in the profile


CU51 or CS62? Or Both?

Can I use CU51 and CS62 interchangeably to edit configurable order BOMs?

Yes, but note that you must use CU51 before using CS62 (or CSAB)


The Plant field in CS62 is only displayed with a Modifcation (otherwise it assumes SOLI plant)

There are various reasons to maintain

Order BOMs in a plant that differs from the

SOLI

CU51 or CSAB?

CSAB is like CU51 but without configuration – key features include:

• Material Replacement – like instantiation for non-configurable materials

• Detached Order Assemblies – for long lead time items

• Order Analysis – useful information:


Order BOM User Exits Explained


• CCUX0006 – Prevent merge of material BOM changes into order BOM in CU51• CCUX0007 – Create a material BOM or order BOM for instantiated materials• CCUXDATE – Define valid from date for items added to order BOMs in CU51• CCUXDATU – Define the explosion date for material BOMs in CU51• CCUXIACD – Make changes to any instantiated material masters immediately after they are created• CCUXINST – Default and/or suppress instantiation parameters dialog for each material marked for

instantiation before it occurs (or prevent even instantiation)• CCUXSTAT – Defines the BOM Status for instantiated materials

There are also two common modifications (i.e. allow order BOM explosion in sales and allow instantiation of a configurable single instance)

The Help for enhancements can be confusing, here is what it means

The Dreaded CX072 Error


Instantiation is not permitted in some situations, but you are left to guess why!

This error occurs when you mark an item that:

• Is a component and not a header

• Has no material BOM

• Has no configuration instance

• Is the root only

Group Order BOM (Concept)


Do you have the need to switch the plant of manufacture after order BOMs have been manually adapted?

• In concept, this is similar to material Group BOMs (where you allocate a BOM to additional plants)

• Unfortunately the native solution is to manually create and maintain Order BOMs in the alternate plants (with CS6x modification previously shown)

• Custom solutions are possible; some customers and eLogic have developed them (demo available)

Long Lead Time Items


Long Lead Time Items Explained


• Long lead items often occur at the bottom of a BOM structure once the design is completeo This is contrary to the need to procure these items immediately after a sales order is

placed (or even sometimes before)

• Typical planning processes cannot run on higher level assemblies that are missing or incomplete or potentially incorrecto In other words, higher level assemblies are often not ready for planning (i.e. they are still

under development and subject to frequent and iterative changes)

o Procurement would rather wait for stable requirements for items that have short lead times (to avoid effort involved in cancelling orders, shifting dates, etc. for no benefit)

• A means is needed to plan for long lead time items while the BOM structure is under developmento But then do not “double order” the long lead items when the structure is complete

Long lead time items commonly occur in configurable engineered products

Long lead time items are generally not kept in stock

due to high cost, low volume, and high

specialization

Item demand is difficult or impossible to predict or

forecast

Examples include specialized castings and

bearings


This is the SAP recommended approach

• Create an Order BOM for the level(s) that consists of long lead items

• Enter planned independent requirements for the level(s) – Planning without final assembly

• MRP generates requirements for these materials and then consumes the PIR with the actual demand

• The detached assemblies are later “attached” to higher level assemblies when BOM structure is complete

This approach requires relatively high manual effort

Order BOM consists of long lead time items

Option 1 – Detached Assemblies


Long Lead Items

Long Lead Items

Long Lead Items

• Skeleton BOM typically comes from an external engineering system as an Order (or WBS) BOM

• Long lead items are maintained at the correct level in BOM structure and as a result demand is generated for exact requirement dates

• Skeleton BOM is replaced by a higher priority BOM when engineering is completed for a given assembly

Option 2 – Skeleton BOM

A “Skeleton” BOM contains all assemblies and long lead times only


• Prerelease phantom is part of super BOM• Planning only reads production relevant BOM items• Only the prerelease phantom is production relevant

until the remainder of BOM is “released”• Release make main assembly production relevant

and prerelease as NOT production relevant• Care must be taken to maintain BOM items without

production relevance until their “release”• Disadvantage is that MRP dates for long lead items

may be earlier than required• Customizations can improve usability

Prerelease level –Long Lead ItemsProduction relevant

Super BOM

Option 3 – Prerelease (w/ Relevance)

A Prerelease BOM contains only long lead times and is mutually exclusive with the rest of the BOM


Option 4 – ECM Stages

An Order BOM can be maintained with successive change numbers that are read by dependencies

• This is perhaps the most sophisticated approach

• Dependencies explode items and branches based on the ECM (stage) that is being used for configuration

• It is appropriate only for companies with rigorous approaches to long lead time items

• We are glad to discuss offline if anyone is interested

Meet us for Happy Hour with a Credit Card

Intercompany / Multi-Plant


BOM Explosion – Special Procurement


BADI must be implemented

Changing Plants in Configuration

Is it possible? The answer is “mostly yes”… using Special Procurement


Requirements:

• CUKO Plant change BADI

• Order BOM screen enhancement to include plant

• CU51 will establish order BOMs in the correct plant based on special procurement key

• May require enhancement during Goods Receipt, if product need to be received at purchase price rather than at cost of manufacturing (some companies requires a markup between plants)


• Requirements:

o CUKO Plant change BADI

o Order BOM screen enhancement to include plant

o CU51 will establish order BOMs in the correct plant based on special procurement key

o May require enhancement during Goods Receipt, if product need to be received at purchase price rather than at cost of manufacturing (some companies requires a markup between plants)

• Special Procurement – Purchased from alternate plant

o Involves purchase orders

o May require special procurement for costing (manufactured in alternate plant)



Manufacture in Alternate Plant

• Involves Plan/Production orders

• Stock automatically updated in receiving plant once production confirmed in manufacturing plant

• May need to receive into Transit location (temp location) until stock is physically received into receiving plant

• Can be set dynamically at BOM item level (Direct Production)



Withdrawal from Alternate Plant

• Involves Plan/Production orders.

• Can be maintained at BOM item level

• Withdrawal for components happens in the alternate plant based on plant maintained in special procurement key

• Only feasible to use when both plants are in close proximity to each other

• If not material has to be maintained in a separate storage location in plant of withdrawal until the product physically reached the plant requesting it


Alternate plant for items in a Sales Set

• Example: Sales set consists of Materials A, B, C and D

• Material B is manufactured and shipped to customer from an alternate plant of manufacture than the plant assigned to the sales set material

• Plant change userexit is required to change plant, based on certain logico USEREXIT_SOURCE_DETERMINATION in include: MV45AFZB

• Requires material B to be in both plants and Super BOM to be in Plant of Manufacture.


Required configuration must be in place to

support cross company sale (in case plants belong to different

company codes)

Sales


CRM to ECC Integration, #1

BOM Applications

• CRM requires that all configuration profiles in a multi-level structure use the same BOM Application, otherwise BOM explosion stops.

• BOM usage may change from level to level.


Sub Item

Component

Component

Sub Item


Sales Relevance

• CRM requires that each instance be sales relevant for that instance to be sent to ECC during harmonization

• IPC allows configuration of non-sales relevant instances, they just aren’t passed in the integration


Component

Component

Component

Sub Item

Product1000

2000

3000

4000

5000


Unwanted Materials in Configuration Browser

• Non-Configurable Materials in the same BOM explosion as Configurable Materials (such as in a universal BOM) will appear as instances in CRM configuration user interface with no characteristics assigned.


Component

Component

Component

Sub Item

Product1000

2000

3000

4000

5000

Setting Item Category on Subitems

There is one native way and several possible “hacks”

1. You can infer a sales relevance on your sales BOM item that will change the item category usage

2. You can create a reference characteristic to VBAP-PSTYV and set item category via user exit in MV45AFZZ (a hack)

3. Others?


Method 1 is the native approach, especially

with regard to allowed manual item categories

Method 2 hacks are the only known way to

change item category of the MAIN sales item

Redetermining item category on change is a

risky hack

Potpourri


Beware of “Breaking the Chain”

Multi-level configuration stops when missing/incompatible configuration profiles or non-configurable materials are encountered in a given BOM branch


Plan/Prod

Order BOM

No Profile

Legend:

Configurable

NonConfigurable

A

C

B

Example 1

OD

OD not processed andno C value assignments

L

N

M

Example 2

OD

OD processed but no Mor N value assignments

X

Z

Y

Example 3

OD

OD processed but no Yor Z value assignments

“Display” Configuration

Display configuration actually runs object dependencies and so what is displayed may differ from what is stored in the database

MRP and other functions/programs use the stored configuration only which can lead to different outcomes when compared to displaying configuration


Product

AUS

Chamber

Product

Assembly

Subassembly A

Subassembly B

SDCOM-VKOND

VAR_KEYS

VAR_KEYS

SUB_A_FEATURE1

SUB_B_FEATURE1

$500

$500

SUB_A_FEATURE1

SUB_B_FEATURE1$1000

Pricing Rollup

The same variant key that is set from multiple

subassemblies would only appear once at the

root (there is no additive effect)

There is a way to avoid enumerated pricing condition records

Any variant factors must be set by procedure at

the root© 2016 eLogic l All Rights Reserved l Proprietary and Confidential

Configuration Profile Needed?

• A profile is required to persist characteristic value assignments.

• A profile is required if a configurable material needs object dependencies for:

o Variant Pricing

o Defaults to be set (procedurally)

o Any calculations to be performed etc.

• A profile is optional if a configurable material:

• Acts as Material with Plan/Production Order

o Useful when there are lot of configurable materials used in BOMs and does not involve the use of Order BOM functionality

o Uses super BOM and routing which are based on the configuration of header material


Not all configurable materials require a profile

Migrating Variant Key Descriptions

How do you migrate variant key descriptions (i.e. VK30 texts) from system to system?

1. Manually

2. Create a manual transport for table TVARC and TVARCT


Manual transports are possible because there are no internal numbers used and the target data can

be entirely overwritten

Pushbutton Enhancement Caveat


Timing issues can occur if you try setting characteristic value assignments from pushbutton user exits using CUPR functions

Pushbuttons offer a way to trigger

complementary functions like

selectors, mass updates, and

reporting functions

Get Rid of a value – Don’t delete it


Deleting a value can corrupt existing configurations. Using ECM can be problematic because of variations in configuration dates.

Example – Value 730K should not be offered any longer

Ask questions today & keep up the conversation tomorrow!

Learn more on our blog

blog.elogic.com

Reach out to us

[email protected]

Thank you for attending!

© 2016 eLogic l All Rights Reserved l Proprietary and Confidential 57

elogic.com/blog

mailto:[email protected]