account assignment category in pr

Account Assignment Categories and Document Types for PR in SAP

How to assign categories and document types for purchase requisition.

The following training tutorials guide how to assign account categories and document types for PR. You can assign categories and document types for PR by using one of the following navigation methods.

• SAP IMG Path : – Project system >> material >> procurement >> Account Assignment Categories and Document Types for Purchase Requisitions
• Transaction code: – OPS8

Refer below step by step procedure to assign account assignment categories to document types for purchase requisition in SAP.

Step 1: – Enter transaction code “OPS8” in the SAP command field and press enter key.

Step 2: – On material flow in the network overview screen, click on new entries to assign categories and document types

Step 3: – On new entries of the Account assignment screen, update the following fields.

• Procurement: – Update the three digits alpha-numeric id that identifies the procurement indicator and updates the descriptive text.
• Priorities: – Priorities control various stock types, for example, you can set priority project to 1, priority plant to 2, and priority sales to 3.
• Control data: – Control data control the purchase requisition network, third-party material is delivered to customers, and preliminary purchase requisitions.
• Default item category: – Update the default item category for the item category MRP (Material Requirement Planning)

After maintaining the required details Account Assignment Categories and Document Types for PR Click on the save button to save the configured data.

Continue to read SAP PS Tutorial with real-time scenarios.

3077580 - "account assignment category" of Purchase requisition is "U"

The "account assignment category" of the purchase requisition created by MRP is "U" (unknown)

Environment

SAP S/4HANA Cloud 

Reproducing the Issue

• Run MRP for a Non-Valuated Materials  to create purchase requisition.
• The "account assignment category" of the purchase requisition is "U"

In SSCUI  102156 , the Account Assignment for Non-Valuated Materials is set as "U"

Change the account assignment category accordingly.

account assignment category, Non-Valuated, value updating, MRP, schedule MRP run, MD01N, purchase requisition, account assignment, unknown, U, 102156 , KBA , PP-MRP-PP , Procurement Proposal , PP-MRP-PP-2CL , Procurement Proposal (Public Cloud) , Problem

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark

Creating Purchase Requisitions

After completing this lesson, you will be able to:

• Create a Purchase Requisition for Stock Item and Consumable Material

Purchase Requisitions

As a long-term SAP user, you want to understand the usage of purchase requisitions in the purchase to pay business process as well as the usage of document types, item categories and account assignment for consumable items.

A purchase requisition is an internal document that the purchasing department uses to procure a particular quantity of a material or a service for a particular date.

A purchase requisition can be created directly or indirectly.

Directly means that a purchase requisition is created manually in the department that has the need. Whoever creates the purchase requisition determines which material or service in which quantity, and for which date have to be ordered.

Material requirement planning (MRP)

Maintenance orders

Planned orders

You can also initiate purchase requisitions from SAP Ariba.

When you create a purchase requisition for materials that have a material master record, the system transfers the data in the material master record to the purchase requisition. You also have the option to select items from a web-based catalog.

You can convert purchase requisitions into requests for quotations (RFQs), purchase orders (POs), or outline agreements.

Purchase Requisition Processing

Account assignment objects.

If you buy material, you procure it either for stock or for direct consumption.

You need to enter an account assignment for an item under the following circumstances:

If you order a material that is not subject to value-based inventory management and post its value directly to consumption (pure consumable material)

If you order an article that does not have a material master record

If you order a service

If you want to procure a material as a consumable, you must specify an account assignment category and other account assignment data in the document item of the purchase requisition or purchasing document.

The account assignment category determines the account assignment object category that is to be charged. You must provide the account assignment data. The accounts are debited when the goods receipt or invoice is posted.

The following are the examples of account assignment objects:

The account assignment object cost center (account assignment category K): When you make an account assignment to a cost center, you must enter the general ledger (G/L) account number of the consumption account. You must also enter the cost center for which the material will be procured on the account assignment data screen. You can specify that the system automatically proposes the number of the GL account to be charged in Customizing.

The account assignment object asset (account assignment category A): If you use account assignment category A, you have to enter the asset number on the account assignment data screen. The system automatically determines the G/L account to charge based on the asset number you cannot enter manually.

Procurement for Consumption

When you procure a material directly for consumption, no material master record is necessary.

The characteristics of consumable materials with a master record are as follows:

There is no value-based inventory management.

The system automatically updates consumption in the material master record.

In SAP S/4HANA, the term "consumable material" is any material subject to procurement whose value is settled using cost element accounts or asset accounts. Therefore, a consumable material is procured directly for an account assignment object.

When procuring a consumable material without a material master record, you have to enter a short description, a material group, and a purchase order unit in the document manually. You have to do this because you cannot fetch this data from a master record. This is not true for a material with a master record. For these materials, the material type controls whether inventory management takes place on a value basis.

Procurement for Consumable Materials

When you procure a consumable material, a material master record is not required, but can be used.

You can procure stock material for consumption. In all cases, you must specify an account assignment category and other dependent account assignment data, such as an account assignment object and a G/L account (consumption account). At the time of goods receipt or invoice receipt, the system debits the consumption account the purchase order specifies with the procurement value. Additionally, the system posts the amount to the account assignment object.

The Procure to Pay business process integrates with many different SAP application modules.

A purchase requisition can be created from a MRP run.  If a purchase requisition line item is a consumable for a cost object, then upon saving the purchase requisition, a commitment in Management Accounting is created. Please note: Commitment Management within Management Accounting needs to be activated.

 If a purchase order line item is a consumable for a cost object, then upon saving the purchase order, a commitment in Management Accounting is created. Please note: Commitment Management within Management Accounting needs to be activated.

When you save a goods receipt for stock materials, on hand inventory is increased.

If a change in material valuation occurred, then the system creates an accounting document in Financial Accounting.

If the purchase order was for consumable materials, the system not only creates an accounting document in Financial Accounting, but also creates a controlling document in Management Accounting and creates a document to update the Material Ledger.

If the organization is using Warehouse Management, then the system creates a transfer requirement.

Lastly, the system updates the purchase order history.

When an invoice is posted, the system creates an accounting document, in Financial Accounting to record the liability owed to the vendor.  The system, also creates an open item against the vendor’s account.

If the purchase order was for consumable materials, and the invoice amount differs from the purchase order amount, then the system creates a controlling document, in Management Accounting.

Create a Purchase Requisition for a Stock Item and a Consumable Material

Log in to track your progress & complete quizzes

Purchase requisition for account assignment Table in SAP

• EBKN Table for Purchase Requisition Account Assignment Table Type : TRANSP Package : ME Module : SRM-EBP
• VSEBKN_CN Table for Version: Purchase requisition account assignment Table Type : TRANSP Package : CNVS Module : SRM-EBP
• T161F Table for Release Point Assignment for Purchase Requisition Release Table Type : POOL Package : ME Module : SRM-EBP
• CDBD_PR_H Table for Purchase Requisition header - CDB table Table Type : TRANSP Package : CDB Module : CRM-MSA
• CDBD_PR_I Table for Purchase Requisition item - CDB table Table Type : TRANSP Package : CDB Module : CRM-MSA
• EBAN Table for Purchase Requisition Table Type : TRANSP Package : ME Module : SRM-EBP
• EBAN_TECH Table for Purchase Requisition for External Sourcing Table Type : TRANSP Package : MEREQ Module : MM-PUR
• FDM2 Table for Cash management line items from MM purchase requisition Table Type : TRANSP Package : FF Module : CRM-MD-PCT
• MEREQX Table for Purchase Requisition Change Parameter Table Type : TRANSP Package : MEREQ Module : MM-PUR
• PREXT Table for Enhancement Fields for Purchase Requisition Table Type : TRANSP Package : ME Module : SRM-EBP
• PSPR_GRP_IND_PR Table for Grouping Indicators and purchase requisition numbers Table Type : TRANSP Package : PS_ST_EHP3_SFWS_SC Module : PS-ST
• SER09 Table for Doc. Header for Serial Numbers for Purchase Requisition Item Table Type : TRANSP Package : IQSM Module : CRM
• SNWD_PR_I_TPL Table for EPM: Purchase Requisition Item Database Table Template Table Type : TRANSP Package : S_EPM_AIE_TPL Module : BC-SRV-NWD
• T161G Table for Release Prerequisite, Purchase Requisition Table Type : POOL Package : ME Module : SRM-EBP
• T161H Table for Fields for Release Procedure, Purchase Requisition Table Type : POOL Package : ME Module : SRM-EBP
• T161S Table for Release Indicator, Purchase Requisition Table Type : POOL Package : ME Module : SRM-EBP
• T16CR Table for Version-Relevant Fields of Purchase Requisition Table Type : TRANSP Package : MEDCM Module : MM-PUR
• TEE001 Table for Purchase Requisition from Easy Execution Table Type : TRANSP Package : CKEXECUTION Module : CO-PC-PCP
• TME_TOL Table for Overdraw tolerance for Purchase Order / Requisition Table Type : TRANSP Package : FMFG_E Module : PSM-FM
• VSEBAN_CN Table for Version: Purchase requisition Table Type : TRANSP Package : CNVS Module : SRM-EBP
• /SAPSRM/SH_PO_RC Table for Table for ERP Search Help Purchase Requisition Release Code Table Type : TRANSP Package : /SAPSRM/PDO_SHARED Module : SRM-EBP-PD
• /SAPSRM/SH_PR_RC Table for Table for ERP Search Help Purchase Requisition Release Code Table Type : TRANSP Package : /SAPSRM/PDO_SHARED Module : SRM-EBP-PD
• /SAPSRM/SH_PR_RG Table for Table for ERP Search Help Purchase Requisition Release Group Table Type : TRANSP Package : /SAPSRM/PDO_SHARED Module : SRM-EBP-PD
• /SPE/CRMD_PR_MAP Table for Mapping Table Purchase Requisition CRM Sales Order Table Type : TRANSP Package : /SPE/CRM_GENERAL Module : LO-SPM-OUT
• JKSDPORDERFLOW Table for IS-M: Assignment of Purchase Order Book to Purchase Order Table Type : TRANSP Package : JSDI Module : IS-M
• DPR_OBJLINK_SCPO Table for Purchase Order and Purchase Order Item for SRM Shopping Cart Table Type : TRANSP Package : DEVELOPMENT_PROJECTS_SRM Module : PPM-PRO-EXT
• TOIAE Table for Purchase Fee Account Assignment Table Type : TRANSP Package : OIA Module : CRM
• CRMC_ACC_MAP Table for Assignment of Account Assignment Group to Account Table Type : TRANSP Package : CRM_LEASING_SRM Module : CRM-LAM-BTX
• CDBC_REQPRIO Table for MM Requisition details table Table Type : TRANSP Package : CDB Module : CRM-MSA
• EREC_GENERAL Table for General Requisition Form Settings Table Type : TRANSP Package : PAOC_MSS_E_RECRUITING Module : EP-PCT-MGR-HR
• EREC_ISR_TYPES Table for ISR Requisition Scenario Types Table Type : TRANSP Package : PAOC_MSS_E_RECRUITING Module : EP-PCT-MGR-HR
• EREC_ISR_TYPES_T Table for Text table for ISR Requisition Types Table Type : TRANSP Package : PAOC_MSS_E_RECRUITING Module : EP-PCT-MGR-HR
• EREC_METHODS Table for Start Methods for Requisition Creation Table Type : TRANSP Package : PAOC_MSS_E_RECRUITING Module : EP-PCT-MGR-HR
• MEREP_TREQUIS Table for MI Testtool - Requisition Table Type : TRANSP Package : S_ME_TESTTOOL Module : BC-MOB
• MEREP_TVENDOR Table for MI Testtool - Requisition Table Type : TRANSP Package : S_ME_TESTTOOL Module : BC-MOB
• NMATO Table for IS-H: Material requisition by nurse station Table Type : TRANSP Package : NPAS Module : CRM
• T161A Table for Linkage of Requisition Doc. Type to Purchasing Document Type Table Type : POOL Package : ME Module : SRM-EBP
• T16LA Table for Texts on Status of Requisition Processing Table Type : TRANSP Package : ME Module : SRM-EBP
• T16LD Table for Routines for Structure of Requisition Lists Table Type : TRANSP Package : ME Module : SRM-EBP
• T16LE Table for Texts for Routines for Structure of Requisition Lists Table Type : TRANSP Package : ME Module : SRM-EBP
• T16LF Table for Routines for Data Retrieval in Requisition Lists Table Type : TRANSP Package : ME Module : SRM-EBP
• T16LG Table for Texts for Routines for Data Retrieval in Requisition Lists Table Type : TRANSP Package : ME Module : SRM-EBP
• T75REQST Table for Requisition Status Table Table Type : TRANSP Package : PBNA_REC_MYSAP Module : PA-PA-US
• TNM02 Table for IS-H MM: Material Requisition Parameters Table Type : TRANSP Package : NPAS Module : CRM
• /ISDFPS/MEMMTRQ Table for Customizing: Requisition Types (Mobile) Table Type : TRANSP Package : /ISDFPS/ME_MM Module : IS-DFS-MA-MM
• /ISDFPS/MEMMTRQL Table for Customizing: Requisition Type for Document Cat. (Mobile) Table Type : TRANSP Package : /ISDFPS/ME_MM Module : IS-DFS-MA-MM
• /ISDFPS/MEMMTRQT Table for Customizing: Texts for Requisition Types (Mobile) Table Type : TRANSP Package : /ISDFPS/ME_MM Module : IS-DFS-MA-MM
• /SAPCEM/BD01 Table for Planning: Default Values for Requisition Note Table Type : TRANSP Package : /SAPCEM/DISPO Module : IS-EC-CEM
• /SAPCEM/BDKO Table for Header Data for Requisition Note Table Type : TRANSP Package : /SAPCEM/DISPO Module : IS-EC-CEM
• /SAPCEM/BDPO Table for Requisition Note Item Table Type : TRANSP Package : /SAPCEM/DISPO Module : IS-EC-CEM
• ACCRAC Table for Assignment of Acr./Def. G/L Account to Accruals Account Table Type : TRANSP Package : ACCR Module : FI
• REQTYPE Table Data element for Requisition Type of the Mobile Requisition
• /ISDFPS/ME_MM_REQTYPE Table Data element for Requisition Type of the Mobile Requisition
• CO_BANFN Table Data element for Purchase requisition number
• CO_BNFPO Table Data element for Item number of the purchase requisition in the order
• SCEND_ACT Table Data element for Ind.: Purchase requisition at activity finish date
• BBP_ES_RFP_TEXT_ID_PR Table Data element for Text ID for Storing RFP Reference in Purchase Requisition
• BBSRT Table Data element for Purchase Requisition Document Type
• BANFN Table Data element for Purchase requisition number
• BNFPO Table Data element for Item number of purchase requisition
• CREATE_IND Table Data element for Creation Indicator (Purchase Requisition)
• CFB_BSART_PR Table Data element for Document Type for Creating Purchase Requisition from RMC
• MRPDS_PURCHASE Table Data element for MRP DS: No Purchase Requisition Creation from APO

Purchase requisition for account assignment related terms

Definitions.

SAP is the short form of Systems, Applications & Products in Data Processing. It is one of the largest business process related software. This software focused on business processes on ERP & CRM.

Like most other software, SAP also using database tables to store the data. In SAP thousands of tables are there to store different data. A table contains several fields and some of the fields will be key fields.

Popular Table Searches

Latest table searches.

Blog about all things SAP

ERProof » SAP MM » SAP MM Training » SAP Blanket Purchase Order

SAP Blanket Purchase Order

The basic components of the SAP blanket purchase order process are as follows:

Create Framework Purchase Order

Create invoice.

We walk through these components in the following sections.

Create the SAP blanket purchase order via transaction code ME21N .

Header Section

In the header section of the purchase order, enter the following information for each blanket item for the selected vendor:

• Choose document type FO – Framework Order to categorize the order as a blanket purchase order. Every purchase order is assigned a document type to identify the purpose and functionality of the order.
• Enter the v endor master number in the Vendor field. For our example, we use vendor 9001 – Michaela Meier .
• Click the Additional Data tab in the header section and enter Validity Start and Validity End dates for the blanket purchase order. The validity dates provide the duration during which purchases can be made against the order. In our example, we set a one year validity period, starting on 09/26/2017 and ending on 09/26/2018 .

Our example header data can be seen below:

Item Section

In the item section of the SAP blanket purchase order, enter the following details:

• Select account assignment category K – Cost center to denote that a cost center should be specified and that all invoices should be charged to that cost center. The account assignment category list may contain standard and customized categories.
• Choose item category B – Limit . The item category of a purchase order identifies which type of procurement is taking place and triggers certain features. Item category B , for example, defaults a PO quantity of 1 . This item category also switches off the goods receipt requirement for the blanket PO.
• Enter text for the item.
• Specify the plant for the procurement. In our example, we use plant 9001 – Berlin Distribution .

Our example item data can be seen below:

Item Details

• Click the Limits tab and enter the overall limit value. The total of all procurements for this purchase order during the validity period cannot exceed this value. Select the No limit tickbox if there should not be a maximum spend for the blanket order. In our example, we set a limit of 5000 EUR as can be seen below:

• Click the Account Assignment tab. Based on the account assignment indicator K specified in the item section, specify the cost center and G/L account that all invoices should post to. In our example below, we specified cost center 1000 and G/L account 400000 .

Now that we have an SAP blanket purchase order, we can begin posting invoices straightaway. Remember that the item category B disables the goods receipt requirement. Post invoices referencing the PO number via transaction code MIRO .

Once invoices have been posted, the invoice receipts will appear on the Purchase Order History tab. In our example we have created three invoices which total 5000 EUR , as shown below:

Remember that our blanket purchase order limit was set to 5000 EUR . An attempt to create an additional invoice that exceeds the limit will result in the below error message:

Did you like this SAP MM tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP MM tutorials.

Navigation Links

Go to next lesson:  SAP Source List

Go to previous lesson:  SAP MMBE Stock Overview

Go to overview of the course: SAP MM Training

13 thoughts on “SAP Blanket Purchase Order”

Since there is no GR for a Framework PO, how do you satisfy the traditional auditing requirement for a 3-way match?

Blanket purchase orders are used for simplified procurement of consumable materials or services. This process has different auditing requirements compared to the traditional procurement process for stock materials.

I realize that the auditing process would be different. Because SAP does not allow a GR on a Framework PO, I was looking for suggestions on how to explain that, how to “sell” the process in which the traditional 3-way match is no longer used, at least not technically. We are implementing ReadSoft and plan to use an “approval” workflow, and use the fact that the user approved it (which is recorded) in place of the traditional GR.

You don’t need 3-way match if you procure things like consumables. They are relatively cheap and don’t even have individual material master records. If you don’t bother with creation of master records, then why should you use functionality like 3-way match?

Please answer my bellow questions….

How do you receive materials if category “B” disables the MIGO transaction?

Blanket purchase orders are for Class “C” type materials of ABC analysis, they are of low value and are not to be stocked. They are generally consumable items, Ex office supplies (blank pages, pencils, pens), sanitary supplies (toilet paper, handwash, etc).

So while creating the PO, you do not have to mention the exact material, you just have to mention short text like office supplies and material group. Account assignment category can be unknown. As there is no particular item mentioned, price is also not mentioned. Here we have to mention the Total value limit up to which we want to procure the item from a particular vendor during a specific validity period. Example 10000$ material from 1/1/2020 to 31/12/2020.

No coming to the point, To procure the material, you just call or intimate the vendor by mail to supply required materials. The vendor sends the materials and it is received by the buyer directly (NO GR). There is no such document where you can tally the order quantity and logically this are nonstock material and it’s totally unnecessary to post a GR for this, this saves time and is economical. SAP has specially given this provision of BPO to avoid GR, otherwise you can procure this type of item by consumable item procurement procedure, which involve PR>PO>GR>LIV. Blanket PO is a value based PO and not a quantity based. So material is received and Invoice is directly posted .

Here you can order materials as many time as needed with reference to the same PO within the validity period till the maximum value limit is reached.

what is the difference between using a framework order versus purchase order? which is better to use for a tolling operation?

the question here should be how do accounting confirm the items are delivered and pay the vendor.

Tutorial was great, but one thing I need to know that was not answered is this; How do you close out a Framework Blanket order?

Good Article, I have one question, In the MIRO process PO amount not copied to the MIRO line amount field. to do that we have to click on the Account Assignment column and enter manually, cant we copied the amount from PO lines.

Can I use 1 FO PO with1 gl account and split the cost center in 3 ways?

Hi I have using FO for consumable materials, now the requirement is can we copy PO short text to GL line items? Then how?

Leave a Reply Cancel reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM !

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

• June 25, 2023

Sara Sampaio

• Technical Articles

In this blog post I will share my requirements and solution on adding Custom Pre-Conditions in Flexible Workflow for Overall Release of PR approval.  I have also shown below how to add value help for the precondition defined.

Requirement 

• Add following preconditions to the “Manage Workflows for Purchase Requisitions” F2705 App in S4HANA 2021:
• Account Assignment Category
• Requisitioner
• Add F4 value help to the above defined preconditions.

Environment

S4HANA on Premise 2021, SAP S/4HANA 2021, S4CORE 106

SAP has given some standard predefined conditions while configuring a flexible Workflow for Purchase Requisition Approval, but we can also add our own pre-conditions.

To add custom new preconditions in Flexible Workflow SAP has given a BADI SWF_WORKFLOW_CONDITION_DEF to enhance and add your required fields in the preconditions tab.

Along with this we also need to add evaluation logic for these custom defined pre-conditions in BADI SWF_WORKFLOW_CONDITION_EVAL.

So basically BAdI SWF_WORKFLOW_CONDITION_DEF allows you to create the fields for key and value to add in the start and step conditions and SWF_WORKFLOW_CONDITION_EVAL helps in valuating the value part of these fields.

Now let’s begin.!

SWF_WORKFLOW_CONDITION_DEF Implementation

First we need to activate and assign Custom Logic App to our id in S4HANA (which I have already done, will try to add a blog for this information too 🙂 ).

Open Custom Logic App > Tab Custom Logic >  “+” icon at the top right corner next to search bar:

Custom Logic App

Now you will see a pop-up window to add new enhancement implementation, enter following details to create the new implementation for Pre-Conditions:

Business Context: Procurement: Start and Pre-Conditions in Flexible Workflow (select from dropdown help)

BAdI Description: Providing additional conditions for scenarios (select from dropdown help)

Implementation Description: Add Preconditions for PR Scenario (this is custom text can be changed as per your requirement)

Implementation ID: PRECONDITIONS (custom text can be changed as per your requirement)

Pre-Condition Implementation Details

Once added a new implementation will get created and you will be navigated to the screen as below:

Pre-Condition Implementation Draft

The implementation gets created with a sample logic for reference.

Click on Filter tab and “+” icon to add you scenario id so that these preconditions will only be added to that scenario.

Scenario Id added to Filter Tab

In our case I have added scenario_id = WS02000458 ( this scenario is for Overall PR Release)

Click on SAVE.

To check other scenarios, you can refer to this SAP help link:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/af9ef57f504840d2b81be8667206d485/a84badfeaf0445f4bed2a5c9bb0ed9c2.html

Next, we have following parameters in the code:

• CT_CONDITION

ID: Unique ID of the additional condition

subject: Name of the additional condition

type: Condition to be added at step level (type =

if_swf_flex_ifs_condition_def=>cs_condtype-step)

at both of step level and workflow level (type = if_swf_flex_ifs_condition_def=>cs_condtype-start_step)

• CT_PARAMETER

Name: Name of the additional condition

xsd_type: Data type of the additional condition (supported data types are Boolean, date, string, integer, and time)

mandatory: To indicate the additional condition is mandatory.

service_path – the service path of your OData Service

entity – the Value Help entity of your OData Service

property – the field/property in your OData Service for your field value.

In my case for Account Assignment Category and Plant I have used SAP standard CDS  “S_MMPURWorkflowVH” and its equivalent OData service “S_MMPURWorkflowVH_CDS”.

Entity exposing these fields is “S_MMPURWorkflowVH”

For Requisitioner value help we are using a custom table ZPR_DEPT, hence I created a CDS view value help exposing the values of this table which you can check at the end of this blog.

Add the code as below:

• Create two data variables to append to ct_condition and ct_parameter. data : ls_condition like line of ct_condition . data : ls_parameter like line of ct_parameter . ​
• Define condition for Account Assignment Category, OData service used for value help is standard “S_MMPURWORKFLOWVH_CDS” and entity used is ‘S_MMPURWorkflowVH’ * Acc Assignment Category condition ls_condition - id = 'idAcc' . ls_condition - subject = 'Account Assignment Category is' . ls_condition - type = if_swf_flex_ifs_condition_def => cs_condtype - start_step . append ls_condition to ct_condition . ls_parameter - id = 'idAcc' . ls_parameter - name = 'AccAssgnmtCate' . ls_parameter - xsd_type = if_swf_flex_ifs_condition_def => cs_xstype - string . ls_parameter - service_path = '/sap/opu/odata/sap/S_MMPURWORKFLOWVH_CDS' . ls_parameter - entity = 'S_MMPURWorkflowVH' . ls_parameter - property = 'AccAssgnmtCat' . ls_parameter - mandatory = abap_false . append ls_parameter to ct_parameter .
• Define condition for Plant, OData service used for value help is standard “S_MMPURWORKFLOWVH_CDS” and entity used is ‘S_MMPURWorkflowVH’ * Plant condition ls_condition - id = 'id_Plant' . ls_condition - subject = 'Plant is' . ls_condition - type = if_swf_flex_ifs_condition_def => cs_condtype - start_step . append ls_condition to ct_condition . *Parameter for Workflow level condition - Plant ls_parameter - id = 'id_Plant' . ls_parameter - name = 'Plant' . ls_parameter - xsd_type = if_swf_flex_ifs_condition_def => cs_xstype - string . ls_parameter - service_path = '/sap/opu/odata/sap/S_MMPURWORKFLOWVH_CDS' . ls_parameter - entity = 'S_MMPURWorkflowVH' . ls_parameter - property = 'Plant' . ls_parameter - mandatory = abap_false . append ls_parameter to ct_parameter . ​
• Define condition for Requisitioner, OData service used to value help is custom “ZC_PR_DEPT_VH_CDS” and entity used is ”ZC_PR_DEPT_VH’ (At the end of this blog I have shown how to create CDS view and OData service for this.) * Requistioner Condition ls_condition - id = 'id_Req' . ls_condition - subject = 'Requisitioner is' . ls_condition - type = if_swf_flex_ifs_condition_def => cs_condtype - start_step . append ls_condition to ct_condition . ls_parameter - id = 'id_Req' . ls_parameter - name = 'Requisitioner' . ls_parameter - xsd_type = if_swf_flex_ifs_condition_def => cs_xstype - string . ls_parameter - service_path = '/sap/opu/odata/sap/ZC_PR_DEPT_VH_CDS/' . ls_parameter - entity = 'ZC_PR_DEPT_VH' . ls_parameter - property = 'ReqDept' . ls_parameter - mandatory = abap_false . append ls_parameter to ct_parameter .

Final Code will look like this:

Now, click on “Save Draft” at the bottom of your screen and then click on “Test” to check your code.

After this once you click on “Publish” your changes will get activated and published in the system.

PLEASE NOTE: fields you add in the pre-conditions please add in Alphabetical order i.e., Account Assignment first then Plant and then Requisitioner, if not added in this order while testing the logic you will get error.(this is something I figured out on my own and I did not find in any of the blogs, so sharing here hoping it will save someone’s time and no one will bang their head on wall thinking where they went wrong.)

SWF_WORKFLOW_CONDITION_EVAL Implementation

Ok, so now moving on to adding evaluation implementation.

Same steps: Custom Logic > + > Add Implementation Details > Create.

Please note this time select BAdI “Value evaluation of additional conditions for scenarios.”

BAdI Description: Value evaluation of additional conditions for scenarios (select from dropdown help)

Implementation Description: Evaluation of additional conditions for PR scenario (this is custom text as per your needs)

Implementation ID: VALUATEPRECONDITIONS (custom text as per your needs)

Evaluation Implementation Details

Add the filter for Scenario id :

You will see some sample code for reference.

Parameters:

• IS_SAP_OBJECT_NODE_TYPE

SONT_KEY_PART_1-> Purchase requisition number

SONT_KEY_PART_2 -> Purchase requisition item number

• IS_CONDITION

condition_id -> Unique ID of the additional condition

• IT_PARAMETER_VALUE

Name -> Name of parameter in workflow in Manage workflow app.

Value -> Value of parameter mentioned in workflow in Manage workflow app

• CV_IS_TRUE (Should be set as true if the additional condition evaluation is successful)
• I_PurchaseRequisitionItemAPI01 – CDS entity for PR header and item

Logic added as below:

• Reading PR details from API I_PurchaseRequisitionItemAPI01 into a local table
• Reading parameter table with Pre-condition value for Account Assignment Category and compare it with the value from PR data. Please note that the key name needs to match with the parameter name defined in the pre-condition BAdI. In this case, it is ‘AccAssgnmtCate’

Similarly for Plant and Requisitioner:

Entire code would look something like this:

Configure Workflow:

Now when we open the “Manage Workflows for Purchase Requisitions” F2705 App, we will be able to see our preconditions along with Value help window to select from.

Click F4 for value help window:

Custom CDS View and OData Service for Value Help:

Now, let us see how to create CDS view for Value help.

As already mentioned above in my case we have a custom table to where we are maintaining Requisitioner data.

• I created a base CDS view first to expose the Req_Dept field from this table:
• Create a consumption CDS view which will be exposed as OData service for value help:

Use OData.publish annotation to publish OData service and Consumption.valueHelpDefinition to create value help on the base CDS view created above.

• Activate the CDS views and go to Tcode : /n/IWFND/MAINT_SERVICE to add and generate metadata of the newly created OData service in the system.

Test in gateway client the service should execute with entity ZC_PR_DEPT_VH:

That’s all from my side friends. Hope this blog helps someone who is new and looking out for more information on Flexible Workflows. I will try to add more parts to this series mentioning my entire end to end Overall PR Release requirement and solution including details on Configuring multi-level approval in Flexible WF with alternative preconditions, activating and maintaining email templates and configure My Inbox and test end to end PR creation with approval.

Thank you for your read.

Tasneem Khilonawala

References:

https://launchpad.support.sap.com/#/notes/2767845

https://blogs.sap.com/2019/12/03/sap-s-4hana-cloud-flexible-workflow-with-new-custom-pre-condition-for-purchase-requisition/

https://blogs.sap.com/2020/07/06/f4-help-in-custom-pre-conditions-for-flexible-workflow-manage-workflow-for-purchase-requisition/

Sign In Now

Forgot password.

It's Free to Sign Up and Get Started.

I want to start as:.

I have read and understood the Terms and Conditions of SAPSPACES.com SAPSPACES will use any of the data provided hereunder in accordance with the Privacy Policy. Terms & Conditions

Notification detail