ENTERPRISE FIRST : Global Template

Workflow Specification Functional Document

Workflow Name: Create Production Master Data Workflow
Generated Document Name:
GLB_PBNA_FLNA_MTD_PP_W001309_Create Production Master
Data Workflow

Market / Project: FLNA/Enterprise First

Author: Ramana Reddy/Raghavendra Nayak

1|Page
 ENTERPRISE FIRST : Global Template

0. Document Information

Document Location

Document Name Sol Man Folder Path Document # Solman Link

Create Production https:// GLB_PBNA_MTD_PP_W001309_ http://
Master Data sapgdaap02.azure.intr Create Production Master Data sapgdaap01.azure.intra.p
Workflow a.pepsico.com:44300/ Workflow epsico.com:08000/sap/
sap/bc/webdynpro/ bc/SMD/SolmanDoc/
sap/smud_frame? 100?
UI_BUILD_OPTIONS _CLASS=SMDDOCLOIO
=ROOT_OCC%3d &_OBJID=0050569A75C
%3d B1EDAB7817E902532C
%3d051McZ3J7jcwxT 09A&_LANGUAGE=EN&
nZizDMIW _LIFECYCLE=0050569A
%26%26%26VIEW_I 30D31ED9BAEDDC63B3
D%3d%3d D3564A&_MODE=D&
%3d051McZ3J7jYQv
%257ByZ1Q1%257B
SG
%26%26%26&UI_BUI
LD_VIEW=SEARCH&
OCC_ID=051McdNB7
jgtWNwG9JAWcW&L
AYOUT_ID=&SAVED
_SEARCH_ID=&REP
ORT_ID=&DIAGRAM
_NODE=&SITE=&RO
LE=C&LANG=E&SC
OPE_ID=SAP_DEFA
ULT_SCOPE

Revision History
Revision Summary of Changes Revised
Revision Date Project
Number By(GPID/Name)
1 07/21/2020 PBNA Initial Document 09283243 /
Raghavendra Nayak
2 02/22/2021 PBNA Update as per Bug#916925 09283243 /
Briefly explained in Page#30 and Raghavendra Nayak
highlighted with yellow colour in
the content
3 08/03/2021 PBNA Bug#1174125: Changes to be 09283243 /
incorporated in the Workflow Raghavendra Nayak
Steps
4 03/17/2022 FLNA Updated logic for FLNA 09338232/ Vinesh
deployment: Group BOM Task Mandivarapu
5 06/14/2022 FLNA Added FUT Document to FSD 09338232/ Vinesh
Mandivarapu
6 07/29/2022 FLNA Adoption of Material type ZPSF 09218811/Roma Dravis
CRF17442 80281634/Rahul Mathur
7 01/17/2023 FLNA Additional Updates 02045012/Emy Romanelli
09363506/Piyush Yadav

Design Authority Approval Details

ENTERPRISE FIRST : Global Template

Approval Date Approved By

 ENTERPRISE FIRST : Global Template

Table of Contents
0. Document Information_________________________________________________2
Document Location____________________________________________________________________2
Revision History_______________________________________________________________________2
1. General Information___________________________________________________4
2. Desired Functionality / User Story_______________________________________4
2.1 Business Benefits_________________________________________________________5
2.2 Scope____________________________________________________________________6
2.3 Solution Details___________________________________________________________6
2.4 Initiating Process / Process Type / Transaction / Program_______________________31
2.5 Multi-Divisional / Cross Company Code Considerations (Flex Code)______________31
0.1 Impact to Markets_________________________________________________________31
0.2 Translation Requirements__________________________________________________31
3. Design considerations for Developers__________________________________31
4. SAP Data Archiving Access Requirements_______________________________31
5. Acceptance Criteria__________________________________________________33
6. Assumptions_______________________________________________________33
7. Error Handling/Monitoring Requirement_________________________________33
7.1 Error Conditions and Logging______________________________________________33
7.2 Notification______________________________________________________________33
7.3 Restart / Recovery________________________________________________________33
7.4 Monitoring Requirements__________________________________________________33
8. Security Requirements/ Authorization Details____________________________34
Process Level________________________________________________________________________34
9. Controls Impacts____________________________________________________36
10. Issues_____________________________________________________________36
11. Dependencies_______________________________________________________36
12. Unit Test Plan_______________________________________________________37
12.1 Key Test Conditions_____________________________________________________37
12.2 Technical Test Conditions________________________________________________37
12.3 Risk and Controls Test Conditions_________________________________________37
12.4 Testing Considerations/Dependencies______________________________________38
12.5 Exception and Error Handling Test conditions_______________________________38
 ENTERPRISE FIRST : Global Template

1. General Information
RICEFW ID W001309
Short Description Create Production Master Data Workflow
Process Owner Sara Gooding
Implementation Phase FLNA W1
MM02, MM03, CC01, CC02, CC03, CS01, CS02, CS03, CRC1,
Transaction(s) (if applicable) CRC2, CRC3, C201, C202, C203, C223
Run Frequency As required Language EN

2. Desired Functionality / User Story

The desired functionality is to streamline the Production Master Data (PMD) creation process. This document
details components of the solution in which PMD Data Maintainers are automatically notified that a new
Engineering Change Number (ECN) and BOM Header have been created and that follow-on action is to be
performed. Each follow-on action gets triggered by the successful completion of preceding action. Following
Production Master Data Objects are in scope:
- Engineering Change Number (ECN)
- Bills of Material (BOM)
- Production Resource
- Master Recipe
- Production Version
Priority: High/Mandatory Medium/recommended Low/optional
Complexity: High Medium Low
Volume of data: Date available from:
Online Background
Mode:

Daily Weekly Monthly Biweekly

Frequency:
Others (Specify): Transactional
Technical information: User Exit BADI Requirement routine
1. Type of Enhancement Custom transaction Business transaction event
Substitution & Validation Others
Sap Std program modification

2. Module /Submodule Module: Production Planning

Information Submodule: Master Data

- Material Master at Plant Level

3. Data Object (Purchase - Engineering Change Number
order/sales order etc.) - Bills of Material
 ENTERPRISE FIRST : Global Template

- Production Resource
- Master Recipe
- Production Version
4. Dependencies /
Constraints / Sequencing Create Production Master Data (PMD) Workflow can be triggered:
- When ‘Plant Specific Material Status’ is set to ‘BR’ and
‘Procurement Type’ is updated with value ‘E’ or ‘X’ &
Special Procurement type as ‘50 or ≠ 50 ’ for following

Material Types ZFIN, ZSFG, ZPLN, ZPSF and ZCNC in

MDG and the same is replicated to S/4 HANA system.

Once workflow is triggered, sequence of work items is pre-defined

and must be sequentially executed after successful completion of
preceding work-item.
BRF+ decision tables need to be maintained to control:
- Which Plants this workflow to be triggered?
- What kind of data to be used in the background automatic
activities? (Ex. Creation of Engineering Change Number,
Creation of Header BOM, etc.)
- Based on what parameters this workflow to be triggered?
(Ex. For Material Types ZFIN, ZSFG, ZPLN, ZPSF , ZCNC,
For BOM Usages 1, etc.)
- For material type ZPSF all the existing workflows for PMD
will be applicable, like ZFIN materials.
- For material type ZSFG Phantom with special procurement
key (SPK) 50, requires limited PMD data to be created, that
is only BOM & Prod Version (PV) needs to be created.
Master Recipe creation are not needed for ZSFG Phantom.
The assigned workflow & its tasks for master recipe creation
needs to be Skipped for ZSFG Phantom. It should continue
to generate workflow for Group BOM/Plant BOM & Prod
Version only.
- For ZSFG-Non-Phantom materials with SPK is ≠ 50 then
Full PMD is required.
- What work-items are skipped for a specific Plant or
Company Code?
 ENTERPRISE FIRST : Global Template

- What links to be shown for a specific Workflow Task?

- Deadline for each Workflow Task?
Legal requirements not fulfilled
General information: Lack of essential business information
1. Results if no conversions are
Lack of functions compared to legacy system
created:
Others (Specify):

Reference Document
Refer slide No. 3, 4 & 5 for Create PMD
Manual process of creating Production Master Data by each
Is there an alternative in the responsible individual. Review or approval process steps cannot be
standard system? recorded in S/4 HANA system with manual activity.
This workflow provides sequential way of creating Production
Reasons why alternative is
Master Data and monitor status of each of the requests for creating
not acceptable:
new Production Master Data.

2.1 Business Benefits

 Cost and time savings due to the automation of this high-volume process.
 Increased visibility and tracking of the PMD creation process inside S/4 HANA.
 Immediate notification and accountability for new PMD additions.

2.2 Scope
The workflow development is for the S/4 HANA system. It will cover the PMD automation step of notifying
PMD Data Maintainers of the need to create BOM, Resources, Master Recipe and Production Versions. Also,
this will cover the PMD automation step of notifying PMD Data Maintainers of the need to populate BOM
components and alternate BOMs.
 Notification to PMD Data Maintainers for BOM, Resource, Master Recipe and Production
Version Build
 Providing information to PMD Data Maintainers
 Review and Approval of created data

2.3 Solution Details

Create Production Master Data (PMD) Workflow can be triggered:
- When ‘Plant Specific Material Status’ is set to ‘BR’ and ‘Procurement Type’ is updated with value
‘E’ or ‘X’ & Special Procurement Type with value ’50 or ≠ 50’ for following Material Types ZFIN,
ZSFG, ZPLN, ZPSF and ZCNC in MDG and the same is replicated to S/4 HANA system
- Once workflow is triggered, sequence of work items is pre-defined and must be sequentially executed
after successful completion of preceding work-item.
- BRF+ decision tables need to be maintained to control:
o Which Plants this workflow to be triggered?
o What kind of data to be used in the background automatic activities? (Ex. Creation of
Engineering Change Number, Creation of Header BOM, etc.)
o Based on what parameters this workflow to be triggered? (Ex. For Material Types ZFIN,
ZSFG, ZPLN, ZPSF, ZCNC, For BOM Usages 1, etc.)
 For material type ZPSF all the existing workflows for PMD will be applicable, similar to ZFIN.
 ENTERPRISE FIRST : Global Template

 For material type ZSFG Phantom with special procurement key (SPK) 50, requires limited
PMD data to be created, that is only BOM & Prod Version (PV) needs to be created. Master
Recipe creation are not needed for ZSFG. The assigned workflow & its tasks for master
recipe creation needs to be Skipped for ZSFG. It should continue to generate workflow for
Group BOM/Plant BOM & Prod Version only.
 For ZSFG-Non-Phantom materials with SPK is ≠ 50 then Full PMD is required.
o What work-items are skipped for a specific Plant or Company Code?
o What links to be shown for a specific Workflow Task?

Workflow Diagram:
 ENTERPRISE FIRST : Global Template

Changes as per Bug#1174125

 ENTERPRISE FIRST : Global Template

BRF+ Table Maintenance requirements:

- Plants Determination: This workflow will be triggered only for the Plants maintained in this table.
Custom Table with following fields to be maintained
- Plant

Notes:
- This BRF+ table is required to be maintained through Fiori App directly in PRD
- C&O Team will maintain entries in this table
- Fiori App is required to maintain in PRD directly along with S/4 HANA Custom T-code

- Material Type Determination: This workflow will be triggered only for the Material Types maintained
in this table.
Custom Table with following fields to be maintained
- Material Type
- Need to add new material type entry as ZPSF in the corresponding BRF+ table-
ZGDT_MAT_TYPE_DETERMIN
 ENTERPRISE FIRST : Global Template

Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD

- Procurement Type Determination: This workflow will be triggered only for the Procurement Types
maintained in this table.
Custom Table with following fields to be maintained
- Procurement Type

Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD

- Special Procurement Key Determination: This workflow will be triggered only for the Special
Procurement Types maintained in this table.
Custom Table with following fields to be maintained
- Special Procurement Type
Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD
Usage: To check active flag for special procurement types maintained in this table & use it as a
condition to trigger workflow.
This will be helpful in in determination of required workflows for ZSFG phantom materials.

- Agent Determination: User IDs maintained against each of the Task IDs in this table
Custom Table with following fields to be maintained and this table should be able to be maintained as
per requirement by Business User with a Fiori App
- Plant
- Task ID
- Material Type
- BOM Usage
- User ID
Notes:
- This BRF+ table is required to be maintained through Fiori App directly in PRD
 ENTERPRISE FIRST : Global Template

- C&O Team will maintain entries in this table

- Fiori App is required to maintain in PRD directly along with S/4 HANA Custom T-code

- ECN and BOM Parameter Table: Entries in this table would be used to control workflow tasks and to
create BOM Header with BOM Status and BOM Usage for specific Company Codes or Plants.

Usage: To fetch the BOM status & other parameters like BOM Not Required, Master Recipe Not
required, Costing Not required flags

Custom Table with following fields to be maintained and this table should be able to be maintained as
per requirement by Business User with a Fiori App
- Company Code
- Plant
- Material Type
- Procurement Type
- Special Procurement Type (SOBSL)
- BOM Usage – 1
- BOM Status – 01
- BOM Not Required
- Master Recipe Not Required
- Costing Not Required
Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD

Additional points:
 Based on Company Code or Plant, there should be entry for BOM Usage and BOM Status,
which would be used to create BOM Header, if BOM Not Required indicator is not set
 Based on the field values for ‘BOM Not required’, ‘Master Recipe Not Required’ and ‘Costing
Not Required’, respective tasks in the Workflow should not be triggered.
 Always, entries with Company Code and then Plant takes precedence in this table

- PMD Workflow Tasks Skip: Task IDs maintained in this BRF+ Table will not be triggered for specific
Task ID/Company Codes or Task ID/Company Code/Plants or Task ID/Company Code/Plant/Material
Type or Task ID/Company Code/Plant/Material Type/BOM Usage combinations, in the order of
precedence.
 ENTERPRISE FIRST : Global Template

Usage: Fetch the list of tasks to be skipped in the workflow

Custom Table with following fields to be maintained and this table should be able to be maintained as
per requirement by Business User with a Fiori App
- Task ID
- Company Code
- Plant
- Material Type
- BOM Usage
Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD
-
Check Point to consider: If material type is ZSFG with special procurement type value as 50 then the
assigned workflows need to be SKIPPED with below task IDs:
 Task 7-Confirm if new resource is required,
 Task 8-Create resource,
 Task 9-Flag Advance Planning checkbox,
 Task 9.5-Maintain Production Line XREF table,
 Task 10-Review Resource,
 Task 11-Create Master Recipe&
 Task 12-Review Master Recipe

- PMD Workflow Tasks Deadline: For each of the tasks triggered, there should be pre-defined
deadlines so that if the tasks deadline is crossed, immediate supervisor needs to be sent mail.

Custom Table with following fields to be maintained and this table should be able to be maintained as
per requirement by Business User with a Fiori App
- Task ID
- Company Code
- Plant
- Number of Hours

Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD
- Same solution used for PTP Workflows to be replicated in identifying workdays
 ENTERPRISE FIRST : Global Template

- Task Links Determination Table: In each of the workflow tasks, relevant links to S/4 HANA to be
provided for ease of access for the task processer.

Custom Table with following fields to be maintained and this table should be able to be maintained as
per requirement by Business User with a Fiori App
- Task ID
- Company Code
- Plant
- Material Type
- BOM Usage
- Link Title
- Link

Notes:
- This BRF+ table is required to be customizable so that any new entries or correction to
existing entries are transportable from DEV to QA to PRD
- Business User should not be allowed to add or correct or delete entries directly in PRD
- C&O Team will maintain and route the changes through DEV to QA to PRD

Workflow Steps Description:

0. Handover to Operations team support letter and/or Production Advice (PA) communication:
This is outside S/4 HANA system step. Manual Step.
Integration Manager along with MDG Team are communicated with a support letter and/or Production
Advice (PA) communication that there is a need to create new Materials in S/4 HANA system.

1. Materials created at Plant(s):

This is outside this FSD and should be part of MDG Workflow process.
Based on the request in the support letter and/or Production Advice (PA), MDG Team initiates to
create Materials in MDG system. All these materials once created in MDG, gets replicated in S/4
HANA system.
This FSD to create Production Master Data (PMD) workflow gets triggered at this point, if there are
any materials which got extended as per “ECN and BOM parameter Table” custom table and the Plant
where these materials are extended as is maintained in “Plants Determination” custom table with
following attributes as example:
i. Material Type : MARA-MTART : ZFIN, ZSFG, ZPLN, ZPSF and
ZCNC
ii. Procurement Type : MARC-MMSTA : “E” or “X”
iii. Special Procurement Type : MARC-SOBSL : “50” or “≠ 50”
iv. Plant Specific Material Status (PSMS) : MARC-BESKZ : “BR” (BOM Required)

1.5 Provide details to build PMD:

This is the first task in this PMD Workflow, which is notified to business user ‘Integration Manager’ in
S/4 HANA Inbox, based on “Agent Determination” custom table with following workflow title and
content:
Note: It is an assumption that business user would be able to attach documents in this step as an
interim solution. In future when Open Text is implemented, this would enable documents to be
attached in Material Master and the same can be viewed in S/4 HANA system through ‘Display
Material’ Fiori App.
 ENTERPRISE FIRST : Global Template

Title:
PMD – Attach relevant documents – {Plant} – {Material Type} – {Material Number} – {Material
Description}

Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks

FLNA Update – 1.75 Step – Group BOM Creation

Once Step “1.5 Provide details to PMD” is marked as complete, this 1.75 step triggers which is the
second task in this PMD workflow. This task will allow for the business user to be able to create a
group BOM for the created material. This group BOM step is needed for FLNA to support FLNA plan
factor design. This task should notify the business user in S/4 HANA Business Workplace Inbox,
based on “Agent Determination” custom BRF+ table with following workflow title and content:
 ENTERPRISE FIRST : Global Template

Title:
PMD – Group BOM Request - {Plant} - {Material Number} - {Material Description}

Content:
Following Options should be available for Business Users in this task:
- Mark Complete. Meaning this task is completed and subsequent task can be triggered.
- Cancel and keep the work item in inbox. This option keeps the work item in inbox and no action taken.

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table along with
documents attached in the previous tasks.

Create Group BOM is a Standard transaction, which also should be available in Fiori application.

TCODE: CS01
 ENTERPRISE FIRST : Global Template

Enter Material and BOM Usage and Hit Enter

Once we hit enter system throws warning message as below:

Hit enter again.

Maintain all Components and other required fields and SAVE.

If we click on View details in Waring Message, information box appears like below:

Assumption: This task is currently FLNA specific task. However, this determination designated to FLNA will
be done in BRF+ tables. However, this task would be able to be used for other deployments if they would
choose to use a group BOM structure.
ENTERPRISE FIRST : Global Template

2. Confirm the Plant makes the Product:

Once Integration Manager confirms that he has attached all the required documents for creation of
Production Master Data, this task is notified to Business Users in Operations Team S/4 HANA Inbox,
based on “Agent Determination” custom table with following workflow title and content:
Assumption: Person handling this task, must review the attached documents (Ex. Handover to
Manufacturing) in the previous step and get the list of components and see whether they are extended
to specific Plant.

Title:
PMD – Confirm Plant makes the Product – {Plant} – {Material Type} – {Material Number} – {Material
Description}

Content:
Following options should be available for Business Users in this task:
- BOM components extended to Plant: Meaning this task is completed and subsequent task 3
can be triggered
- BOM components are not extended to Plant: Meaning this task is not complete and
subsequent task to Data Team is triggered to extend materials to Plant
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks

3. Request for new BOM/Alternate BOM creation:

ENTERPRISE FIRST : Global Template

Once the Operation Team Business User from Task 2 confirms all components required are correctly
extended to the Plant, notification is sent to BOM Co-ordinator maintained for Task 3 as in ‘Agent
Determination’ custom table with following workflow title and content:

Note: In case of Co-product BOMs, ZVPM BOMs or ZPSF BOMs etc., Planning Team will reach out
to BOM Co-Ordinator as these may not be initiated by R&D Team

Title:
PMD – BOM Request – {Plant} – {Material Type} – {Material Number} – {Material Description}

Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks

‘Create BOM/Create BOM Alternative’ custom transaction- ZG_BOM_CREATE, which should be

available in Fiori App also, details:
 ENTERPRISE FIRST : Global Template

This screen has THREE radio buttons and following are to be considered:
- Request for New BOM: When this radio button is selected, system should check that there should be
only one active Workflow on the Material and Plant Combination entered in the screen. BOM Header
and ECN to be created once ‘Execute’ button is clicked. If there is no active Workflow on the Material
and Plant Combination, Workflow task to be triggered to Step 1.5. When user comes to this custom
transaction through workflow item, then this radio button only to be enabled.
- Request for Alternative BOM: When this radio button is selected, system should check that there
should not be any active Workflow on the Material and Plant Combination entered in the screen. BOM
Header and ECN to be created once ‘Execute’ button is clicked. If there is active workflow, system
should give an error message “Already there is active workflow for the Material xxx in Plant xxx”.
When user comes to this custom transaction through workflow item, then this radio button only to be
enabled.
- Request for New Master Recipe: When this radio button is selected, system should check that there
should not be any active Workflow on the Material and Plant Combination entered in the screen. BOM
Header and ECN NOT to be created once ‘Execute’ button is clicked but task 7 to be triggered. If
there is active workflow, system should give an error message “Already there is active workflow for the
Material xxx in Plant xxx”.

- System should check, if material type is ZSFG’s & Phantom with special procurement type as 50, task
7, 8, 9, 9.5 & 10-Resource, 11& 12-Master Recipe should not be triggered but SKIPPED.
- Only task ids relevant to BOM & PV i.e 1,1.5, 1.75, 2, 3, 4, 5, 6,13, 14, 15 & 16 is required for
phantom ZSFG’s.

- Plant field in selection screen should have standard F4 functionality and validation is required
to check whether entered or selected Plant exists
- Material field in selection screen should have standard F4 functionality and validation is
required to check whether entered or selected Material exists
- BOM Alternative in selection screen should have standard F4 functionality based on Plant and
Material entered from Table MAST for reference. Only the next number from MAST table
should be allowed to be entered. If there is no entry in MAST table, blank field value should be
allowed though the field is identified as required. Also, an option to make this field non-
editable is discussed during interaction with Technical Team and this option is feasible and
decreases entry by business user.
 ENTERPRISE FIRST : Global Template

- R&D Specification Number and R&D Version Number can be entered only if radio button
“R&D Team initiated request’ is selected otherwise these fields are not required
- Valid From field is mandatory and the same to be used to created change number in the
background in the next step.
- In case, because of BRF+ Table in-completeness, before creating ECN, show the error
message ‘No entry made in BRF+ table’ and if found correct only proceed with ECN creation
and then BOM Header creation.

These transaction details must be captured in custom table for reporting purposes with following
structure:
Field Name Field Description Field Type Field Length Comments
WERKS Plant CHAR 4
MATNR Material CHAR 18
STLAL BOM Alternative CHAR 2
ZNEWBOM Request for New BOM CHAR 1
ZALTBOM Request for Alternative BOM CHAR 1
ZREQUEST Request initiated by CHAR 2 RD – R&D Team
CO – Costing Team
OT – Others
ZSPECNO R&D Specification Number CHAR 5 15 Alpha-Numeric
ZSPECVNO R&D Specification Version NUM 26 Numeric with
Decimal Point
DATUV Valid From DATS 8
ZCHGNO Change Number CHAR 10
STLNR BOM Number CHAR
ZCRTDBY Created By CHAR 10
ZCRTDON Created On DATS 8

4. Create Engineering Change Number and BOM Header:

This is automatic step triggered once BOM Co-ordinator executes ‘Create BOM/Create BOM
Alternative’ transaction.
Based on the entries in the transaction, Engineering Change Number needs to be created in the
background using transaction CC01 and once successful, BOM Header is created using the
engineering change number through transaction CS01.

CC01 Transaction Details:

Press ‘Enter’
ENTERPRISE FIRST : Global Template

1. Change Number Description: Should follow Global Template instructions as below:

“XX-###############-######-##”
a. XX: Based on the request raised by entered in Step 3 Screen
– If R&D Team initiated this request – RD
– If Costing Team initiated this request – CO
– If Other Teams initiated this request – OT
b. ###############: Value of R&D Specification Number entered in Step 3 Screen
c. ######: Version Number of R&D Specification Number entered in Step 3 Screen
d. ##: Version Number of Engineering Change Number, if R&D Specification Number is same,
entered in Step 3 Screen
2. Valid From: Date from Task 3 screen entry
3. Engineering Change Number Status: Always ’01-Active’ when creating the change number
4. Click on ‘Object Type’ to get to the next screen to select Objects as below
5. Reason for Change: CREATE {PLANT} {MATERIAL NUMBER}

Mark the check boxes as above for ‘Bill of Material’ object and click on SAVE

CS01 Transaction Details:

ENTERPRISE FIRST : Global Template

1. Material for which this Workflow is triggered (ZFIN/ZSFG/ZPLN/ZPSF /ZCNC)

2. Plant for which this Workflow is triggered
3. BOM Usage from ‘ECN/BOM Header’ custom table
4. Alternative BOM, as entered in Task 3 Screen
5. Change Number: Number which got created before this transaction
6. Valid From: From task 3 Screen
Press ‘Enter’ and ignore the information message

Press ‘Enter’ again

Click on ‘Header’ to modify ‘BOM Status’ as maintained in ‘ECN/BOM Header’ custom table

Click on ‘SAVE’ and following message is displayed

If there is any issue in creating any of these two tasks in the background, BOM Co-ordinator
responsible for Task 3, should be able to co-ordinate and resolve the issue and repeat Task 3.
In case, because of BRF+ Table in-completeness, before creating ECN, show the error message ‘No
entry made in BRF+ table’ and if found correct only proceed with ECN creation and then BOM Header
creation.
ENTERPRISE FIRST : Global Template

5. Build BOM:
Once the BOM Co-ordinator from Task 3 completes raising the request for BOM creation successfully,
notification is sent to business users maintained for Task 5 as in ‘Agent Determination’ custom table
with following workflow title and content:
Note:
- If there are Materials with MRP type ‘X0’, need to ensure that ‘Agent Determination’ Table
User IDs from Planning Team
- If BOM Status is ’02-Inactive’, this needs to be changed to ’01-Active’ by the Business User in
this task and then send for review

Title:
PMD – BOM Create – {ECN Number} – {Plant} – {Material Type} – {Material Number} – {Material
Description}
Note: Title should be having prefix REJECT if Task ID 06 rejects and new work item is triggered in
this step for correction
Logic to fetch Engineering Change Number:
Pass Material (MATNR), Plant (WERKS), BOM Usage (STLAN) and BOM Alternative (STLAL) into
Table MAST, fetch BOM Number (STLNR)
Pass BOM Category (STLTY) = M, BOM Number (STLNR) and BOM Alternative (STLAL) into Table
STKO, fetch Change Number (AENNR) where LKENZ or LOEKZ are not equal to X

Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task 6 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

6. Validate BOM:
Once the BOM Co-ordinator from Task 5 completes building BOM as per the request successfully,
notification is sent to BOM Approvers maintained for Task 6 as in ‘Agent Determination’ custom table
with following workflow title and content:

Title:
PMD – BOM Review – {ECN Number} – {Plant} – {Material Type} – {Material Number} – {Material
Description}

Logic to fetch Engineering Change Number:

Pass Material (MATNR), Plant (WERKS), BOM Usage (STLAN) and BOM Alternative (STLAL) into
Table MAST, fetch BOM Number (STLNR)
Pass BOM Category (STLTY) = M, BOM Number (STLNR) and BOM Alternative (STLAL) into Table
STKO, fetch Change Number (AENNR) where LKENZ or LOEKZ are not equal to X

Content:
Following options should be available for Business Users in this task:
- Approve BOM: Meaning this task is completed and subsequent task 7 can be triggered
- BOM Components are not fully Set-Up, Changes required: Meaning this task is not complete
and subsequent task to Data Team is triggered to set-up materials correctly
- Reject BOM: Meaning this task is not complete and task 5 to be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
(Bug#1174125) Once the BOM is approved,
7. New Resource required or not:
ENTERPRISE FIRST : Global Template

(Bug#1174125) Once the BOM Approver from Task 6 approves BOM created as per the request
Once the Operation Team Business User from Task 2 confirms all components required are correctly
extended to the Plant OR from Task 3 once a request is raised to maintain new Master Recipe,
notification is sent to business users ‘Recipe Co-Ordinator’ maintained for Task 7 as in ‘Agent
Determination’ custom table with following workflow title and content:

Title:
PMD – New Resource required or not – {Plant} – {Material Type} – {Material Number} – {Material
Description}

Content:
Following options should be available for Business Users in this task:
- New Resource is required to be created: Meaning this task is completed and subsequent task
8 can be triggered
- Use Existing Resource: Meaning this task is completed and subsequent task 11 can be
triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

8. Create New Resource:

Once the Recipe Co-ordinator from Task 7 requests for creation of new resource, notification is sent to
business users maintained for Task 8 as in ‘Agent Determination’ custom table with following workflow
title and content:

Title:
PMD – Resource Create – {Plant} – {Material Type} – {Material Number} – {Material Description}
Note: Title should be having prefix REJECT if Task ID 10 rejects and new work item is triggered in
this step for correction
Content:
Following options should be available for Business Users in this task:
- This Resource is relevant for MPS/PPDS: Meaning this task is completed and subsequent
task 9 can be triggered
- This Resource is NOT relevant for MPS/PPDS: Meaning this task is completed and
subsequent task 10 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

9. Flag “Advanced Planning” checkbox on Resource:

Once the Recipe Co-ordinator from Task 8 creates new resource and confirms the resource is
MPS/PPDS relevant, notification is sent to business users from Planning Team maintained for Task 9
as in ‘Agent Determination’ custom table with following workflow title and content:

Title:
PMD – Resource update with ‘Advanced Planning’ indicator – {Plant} – {Material Type} – {Material
Number} – {Material Description}
Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task 10 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

9.5. Maintain Production Line Table:

Once the Recipe Co-ordinator from Task 9 updates ‘Advanced Planning’ indicator in newly created
resource if it is MPS/PPDS relevant, if it is not MPS/PPDS relevant, once Task 8 is confirmed,
notification is sent to Business Users maintained for Task 9.5 as in ‘Agent Determination’ custom table
with following workflow title and content:

Title:
PMD – Maintain Production Line Table – {Plant} – {Material Type} – {Material Number} – {Material
Description}
Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task 10 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

10. Review Resource created:

Once the Recipe Co-ordinator from Task 9.5 updates ‘Advanced Planning’ indicator in newly created
resource if it is MPS/PPDS relevant, if it is not MPS/PPDS relevant, once Task 8 is confirmed,
notification is sent to Resource Approvers maintained for Task 10 as in ‘Agent Determination’ custom
table with following workflow title and content:

Title:
PMD – Resource Review – {Plant} – {Material Type} – {Material Number} – {Material Description}

Content:
Following options should be available for Business Users in this task:
- Approve Resource: Meaning this task is completed and subsequent task 11 can be triggered
- Reject Resource: Meaning this task is not complete and task 8 to be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

11. Create Master Recipe:

Once the users from Task 7/10/12 updates relevant work item, notification is sent to Recipe Co-
ordinator maintained for Task 11 as in ‘Agent Determination’ custom table with following workflow title
and content:

Title:
PMD – Master Recipe Create – {Plant} – {Material Type} – {Material Number} – {Material Description}
Note: Title should be having prefix REJECT if Task ID 12 rejects and new work item is triggered in
this step for correction
Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task 12 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

12. Review Master Recipe:

Once the Recipe Co-ordinator from Task 11 requests for review of new Master Recipe, notification is
sent to Recipe Approvers maintained for Task 12 as in ‘Agent Determination’ custom table with
following workflow title and content:

Title:
PMD – Master Recipe Review – {Plant} – {Material Type} – {Material Number} – {Material Description}

Content:
Following options should be available for Business Users in this task:
- Approve Master Recipe: Meaning this task is completed and subsequent task 13 can be
triggered
- Reject Master Recipe: Meaning this task is not complete and task 11 to be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

13. Create Production Version:

Once the Recipe Approver from Task 12 approves Master Recipe, notification is sent to business
users maintained for Task 13 as in ‘Agent Determination’ custom table with following workflow title and
content:
Note:
- As per this task, business user should review the existing Production Versions for the product
in the Plant, if any, and verify naming convention as per standards.
- Also, this new production line with proper naming convention is to be maintained in XREF or
Custom Table (which is still to be finalized) to link with legacy systems, ex. PTS, etc.

Title:
PMD – Production Version Create – {Plant} – {Material Type} – {Material Number} – {Material
Description}
Note: Title should be having prefix REJECT if Task ID 14 rejects and new work item is triggered in
this step for correction
Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and subsequent task 14 can be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks
ENTERPRISE FIRST : Global Template

14. Review Production Version:

Once the Recipe Approver from Task 13 creates Production Version, notification is sent to Production
Version Approvers maintained for Task 14 as in ‘Agent Determination’ custom table with following
workflow title and content:

Title:
PMD – Production Version Review – {Plant} – {Material Type} – {Material Number} – {Material
Description}

Content:
Following options should be available for Business Users in this task:
- Approve Production Version: Meaning this task is completed and subsequent task 15 can be
triggered
- Reject Production Version: Meaning this task is not complete and task 13 to be triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks

15. Change ‘Plant Specific Material Status’ to ‘CR – Costing Required’:

ENTERPRISE FIRST : Global Template

(Bug#1174125) When both Task 6 and Task 14 are complete only, this task should be
triggered.
Once the user from Task 14 approves Production Version, ‘Plant Specific Material Status’ in Material
Master should get updated as ‘CR-Costing Required’.

For Material type ZPSF and ZSFG Phantom (SPT 50): After MTD PMD and FTS MD WFs are
complete for Material type ZPSF, the Plant Specific Material Status is set to MA by master WF instead
of CR.

This change in Material Master shall be captured in another Change Request and details of
enhancement required shall be in separate FSD.

16. Set Engineering Change Number to Inactive:

Once the ‘Plant Specific Material Status’ for the material is updated with ‘CR-Costing Required’,
engineering change number created for maintaining Bills of Material should be set to ’2 – Inactive’
status so that no one can use this change number through transaction code CC02.

For ZPSF materials and ZSFG Phantom (SPT 50), once the ‘Plant Specific Material Status’ for the
material is updated with ‘MA-Material Active’, engineering change number created for maintaining Bills
of Material should be set to ’2 – Inactive’ status so that no one can use this change number through
transaction code CC02.

CC02 Transaction Details:

Enter ‘Change Number’ and click on ‘Continue’

Change ‘Change no. status’ field value from ‘1-Active’ to ‘2-Inactive’ and Click on SAVE
ENTERPRISE FIRST : Global Template

17. Data Team: Step C in the flow chart

Once the user in step 2 OR step 6 selects relevant option, notification is sent to business users
maintained for Task C as in ‘Agent Determination’ custom table. This task is triggered for MDG Team
to maintain details of components which are not set-up correctly with following workflow title and
content:

Title:
PMD – Data correction – {Plant} – {Material Type} – {Material Number} – {Material Description}

Content:
Following options should be available for Business Users in this task:
- Mark Complete: Meaning this task is completed and relevant task 2 OR task 5 can be
triggered
- Cancel and keep the work item in inbox: Keeps the work item in inbox and no action taken

Links:
Links to be given in this step for reference and action from ‘Task Links Determination’ custom table
along with documents attached in the previous tasks

18. Costing Team:

Once the user in Task 14 approves Production Version and material is updated with ‘CR-Costing
Required’, notification is sent to business users maintained for Task 17 as in ‘Agent Determination’
custom table. This task is trigger for Costing Workflow which is captured in another FSD with
reference to RTR Change Request.
 ENTERPRISE FIRST : Global Template

Changes as per Bug#916925:

1. ZPLN Material Type to be considered when triggering Workflow.

2. R&D Spec# is Alpha-numeric 15-digit Ex. 123456789012345, etc.
3. R&D Spec Version# is Numeric with two decimal points Ex. 001, 1.10, 100.01, etc.

FLNA: SLBF relevant specific changes:

4. ZPSF Material Type to be considered when triggering Workflow, all existing PMD
workflows needs to trigger.
5. For ZSFG material type with SPK-50, relevant tasks related to master recipe creation
needs to be skipped.

Specific Workflow Technical Detail

Enter the required information and type one “X” in each checkbox group below:

When ‘Plant Specific Material Status’ is set to ‘BR’

and ‘Procurement Type’ is ‘E’ or ‘X’ & Special
Trigger mechanism
Procurement Type is ’50 or ≠ 50’ in MDG for
following Material Types ZFIN, ZSFG, ZPLN, ZPSF
and ZCNC
Based on the entries maintained in the Custom
Control Tables for specific Material Types and
Start Condition
when Material got extended to new Plants with
‘Plant Specific Material Status’ equals ‘BR’
- Material Master
- Bills of Material
SAP business Object - Production Resource
- Master Recipe
- Production Version
- Engineering Change Number
SAP Standard Workflow
Task/ Not Applicable
Template

Level of approval
As per the Work Items identified in the Process
required
Flow
 ENTERPRISE FIRST : Global Template

Agent determination
technique Role Security Role
Org Unit HR org structure.
Custom Table Agents maintained in custom table
Distribution
lists
To be decided in technical design; Will provide
Unspecified
detailed requirements in this doc.
X Other Specify: BRF+ decision tables

If the agent determination technique is different for

each foreground step then please repeat this
section.

Mention logic for agent

As per the Custom Table
determination (if any)
Internal SAP
X SAP Inbox
user
Outlook
External E-
X
mail Id
Notification destination

Note: There should be option NOT to send to

external Mail ID but by default notification should
be sent to SAP Inbox as well as external Mail ID
maintained in User ID linked to Task IDs
Workflow Notifications
text As per the Solution Details for each step

If approver does not approve, send reminder to

Escalation Handling (if
approver until deadline for the Task ID, after
any)
deadline, as maintained in custom table, notify Line
Manager of the approver through mail.
Integration with portal
Not Applicable

Configuration
Dependencies Not Applicable

Sending notification to the requester user who

Error Handling (if any)
sends the workflow approval in case any issue with
email notification or not existing approval.
Substitution Not Applicable

Custom Screen Design (If Any)

 ENTERPRISE FIRST : Global Template

N/A

User Exit / Enhancement Detailed Description

TEXT TO BE REMOVED, GUIDANCE ONLY< Complete this section if workflow to be triggered from user exit
or if any modification required using user exit. >END OF GUIDANCE TEXT

2.4 Initiating Process / Process Type / Transaction /

Program
As per the Solution Details Section

2.5 Multi-Divisional / Cross Company Code

Considerations (Flex Code)

Global

0.1 Impact to Markets

Global

0.2 Translation Requirements

N/A

3. Design considerations for Developers

N/A

4. SAP Data Archiving Access Requirements

Data Archiving Data Archiving is the process used to delete data that is no longer
needed from online database and storing same in an external
storage that allows for data retrieval and analysis when need be.
Data that have been archived cannot be changed/updated.
Residency Time The period of time that the document is stored in the online
database before the document can be archived. Usually, the
 ENTERPRISE FIRST : Global Template

archiving process checks the last changed date to calculate the

residency time.
Retention Time The total period of time that a document exists in the online
database + archived storage until it is required to be destroyed.
From document creation to document’s end-of-life.

1. Will access to data older than 2 years be required? YES No

2. If YES to question 1:

a. Will the data older than 2 years need to be updated. Why? What process would
require this update, please specify?

b. Please specify reason / explain the need for these data required? Please check
all that applies.

Legal requirement:
Explain: ______________________________________________________

Business
Explain: ______________________________________________________

Tax
Explain: ______________________________________________________

Audit
Explain: ______________________________________________________

Others: Specify ________________________________________________

Explain: ______________________________________________________

3. Please indicate the type of data used in this FSD

Shipments Shipment Costs
Deliveries SD Billing documents
Sales documents Material Documents
Purchase Orders Purchasing Requisitions
Financial Documents Material Ledger
COPA Handling Units
Others:
please specify: Production Master Data

Comments/Notes





 ENTERPRISE FIRST : Global Template

Comments/Notes

5. Acceptance Criteria
 Workflow email notification to the approver as per process flow diagram
 For each of the work item tasks, links to Fiori Apps, documents attached in the previous work items,
comments by previous work items, should be enabled

6. Assumptions
 Documents can be attached in each of the Workflow Tasks and the same can be referred in the
subsequent Workflow Tasks
 BRF+ Decision Tables used to control Workflow are available for maintenance by Business Users
through Fiori Apps
 Workflow Task triggered to Data Team for correcting or extending component materials are
accordingly processed and trigger back to the same Task ID from where the task was initiated
 Workflow Task triggered to Costing Team is captured in another FSD with reference to RTR specific
Change Request
 Workflow Task once updates Production Version as Costing Ready, ‘Plant Specific Material Status’ to
be updated with ‘CR’ and Idoc to be triggered to update the same in MDG system. This interface from
S/4 HANA system to MDG system is captured in another FSD with reference to another Change
Request

7. Error Handling/Monitoring Requirement

7.1 Error Conditions and Logging

N/A

7.2 Notification
In case of any issue with the approver user id (Approver user id is not created), send an email notification
to the user who created the request.

Error How error message should Error Messages Corrective action

be reported

7.3 Restart / Recovery

N/A

7.4 Monitoring Requirements

N/A
 ENTERPRISE FIRST : Global Template

8. Security Requirements/ Authorization Details

TEXT TO BE REMOVED, GUIDANCE ONLY<Please describe any specific security requirements>

END OF GUIDANCE TEXT

To be filled by FSD Author in case SAP Transaction is used

RICEF is used to update, display or print data? Please capture the details here:
X Update
Display
Print
All

Please indicate which SAP module the RICEF applies to.

Module Check (X) Module Check (X)

MM PP X
WM FI
SD CO
PM BI
XI Security
Master Data X ABAP
Other Please Specify

Please indicate which scenario, process and process steps the RICEF impacts since the BPML will be
updated in line with the security change.

rocess Level Description

Scenario
Process
Process Step(s)

Please give a brief description of the functionality the RICEF is used for?

During the creation of Production Master with reference to R&D or other Team’s request,
there is a need to follow a sequence of steps and also review and approval is required to
proceed to next steps to avoid un-necessary rework and mistakes. This Workflow defines
sequence of steps with pre-defined review and approvals steps to avoid mistakes.

RICEF needs additional authorization checks on already known organizational levels (e.g. company code,
purchasing organization, plants etc.)?

Yes
X No

When answer yes, the following organizational levels need to be checked:

 ENTERPRISE FIRST : Global Template

Organizational levels Check (X)

Company Code
Cost Center
Profit Center
Sales Organization
Purchasing Organization
Plants
Other Please Specify

To be filled by Security Team / Development Team

Additional security requirements needed? (to be filled by security)

Yes Proceed in filling the requirements – Developers to implement security requirements
No No further information needed – No implementation of additional security requirements needed.

Information for developer to implement security requirements in RICEF:

Authorization group to be assigned to report / program (to be filled by developer)

RICEF is started by using an SAP transaction (to be filled by developer)

Custom SAP Transaction Name:
None
Transaction type (only to be filled when transaction is
used)
Report transaction
Parameter transaction

Does the report call another custom or standard transaction? (to be filled by developer)
Yes Name:
No

RICEF needs to have additional authorization checks included? (to be filled by security)
Yes Organizational segregation needed – e.g. Report is able to access data from all market units
No Organizational segregation not needed – e.g. Report only handles market unit specific data

When answer is yes, please implement the following authorization check in the RICEF before any
data is displayed or manipulated:
Authorization object Authorization field: Authorization values

Information for security to setup relation between transactions and implemented authorization
checks:

RICEF is using standard components and already has included authorization checks? (to be filled by
developer)
 ENTERPRISE FIRST : Global Template

Includes standard components with standard authorization

Yes checks
do not include standard authorization checks or is called by
No standard transactions.

When answer yes, the following authorization objects need to be maintained in SU24:
Authorization object Authorization field: Authorization values

9. Controls Impacts
N/A

10. Issues
N/A

Issue Date Issue Description Issue Resolution

# Raise
d

11. Dependencies
N/A
 ENTERPRISE FIRST : Global Template

12. Unit Test Plan

11.1 Key Test Conditions

N/A
Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition
1. Happy Path, end-to-end ZFIN = BR PMD created 09338232/
PMD creation Vinesh
Mandivarapu /
06/13/2022
2. Error when creating BOM ZSFG = BR Header BOM not able to
Header as there is no be created
entry maintained in
Control Table for BOM
Usage
3. Happy Path, end-to-end ZPSF = BR Full PMD created
PMD creation
4. Happy Path, end-to-end ZSFG Phantom = Only Group/Plant BOM &
PMD creation BR Prod Version created. No
Master Recipes creation.
5. Happy Path, end-to-end ZSFG Non- Full PMD created
PMD creation Phantom = BR

11.2 Technical Test Conditions

N/A
Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition
1

45 | P a g e
 ENTERPRISE FIRST : Global Template

11.3 Risk and Controls Test Conditions

N/A
Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition
1

11.4 Testing Considerations/Dependencies

N/A

11.5 Exception and Error Handling Test conditions

Exception - special logic or exceptions (e.g. do not process Government Markets customers, only process pre-packs)

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition

Error Handling - functionality in case of errors (e.g. Customer not found, Record already exists)

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition