Backorder Processing (BOP) involves the bulk handling of orders in batch mode, wherein adjustments to order confirmations are made to align with business priorities and respond to shifts in the demand/supply dynamics within your order fulfillment process.

In the context of aATP BOP, a novel notion of requirement classification is introduced, enabling the confirmation of orders based on predefined criteria. This system comprises five classifications (win, gain, redistribute, fill, and lose), each equipped with a distinct rule governing the prioritization of order confirmations. For instance, the winner and the gainer hold the utmost priorities and retain their confirmed quantities without any reduction, while the loser consistently forfeits all confirmed quantities to any other classification.

Let’s go through the each BOP segment to get a thorough understanding.

Different BOP segments and behavior

Example Scenario:

Assumption: The “Scope of check” only considers the on hand stock. Not future stocks.

Organization ABC is receiving some purchase order from different customers and they raise sales orders in the below sequence.

Sales Order creation sequence in the model scenario

In accordance with the aforementioned illustration, organization ABC is generating multiple sales orders for its clientele. The first order pertains to a customer with a delivery priority of 3, who is not classified as one of the premier clients of organization ABC.

The second order is attributed to a customer of neutral standing, characterized as a regular and recurrent purchaser. At the point of initiating the sales order, the available on-hand stock is documented at 4000 pieces, considering that 8000 pieces have already been confirmed for the preceding order out of the total inventory of 12000 pieces. Additionally, the complete requisition cannot be confirmed due to the specified quantity for order 2 amounting to 6000 pieces.

Concluding the sequence, the third sales order is allocated to a premium customer. Upon commencement of the sales order, the on-hand stock will be depleted to zero. This is where the back-order processing functionality within aATP comes into play. Subsequently, an examination of how BOP navigates and manages the aforementioned situation shall be conducted.

BOP variant simulation result for the model scenario.

As depicted above, the BOP (Back Order Processing) variant initiates the process by revoking the entire confirmation attributed to customer 01. This action is prompted by the customer’s adherence to the LOSE strategy, allowing the unconfirmed quantity to become available for utilization by the WIN, GAIN, and REDISTRIBUTE strategies. In this specific business scenario, customer 03 aligns with the WIN strategy. Consequently, the unconfirmed quantity originally associated with customer 01 is reallocated to customer 03.

Nevertheless, achieving full confirmation for customer 03 remains unattainable, given their requirement of 9000 pieces. The deficit of 1000 pieces can be offset by sourcing from customer 02, characterized by a delivery priority of 02 and an inclination towards the REDISTRIBUTE strategy.

The critical aspect lies in discerning the disparity between LOSE and REDISTRIBUTE strategies within this context. Following the complete un-confirmation of the prior commitment to customer 01, a shortfall of 1000 pieces persists for the fulfillment of customer 03’s requirement. This shortfall is addressed through a partial confirmation extended to customer 02.

This elucidates how BOP adeptly manages and automates the resolution of issues arising from incongruities between requirements and demands, a process that traditionally necessitated human intervention.

In order to simplify the understanding process, i have simulated the same business scenario in my system environment and below is the BOP variant simulation result that could observe.

WIN

REDISTRIBUTE

LOSE

In SAP S/4HANA, the Enhanced Available-to-Promise (aATP) feature provides a range of SAP Fiori applications designed for the automated handling of backorders and the manual authorization of orders for delivery. These applications cater to various business document types, including sales orders and stock transport orders.

Each of the subsequent applications enables you to set up a particular step before initiating backorder processing or to oversee the outcomes of a concluded backorder processing operation:

Configure BOP Segment

This application allows you to establish a set of criteria for selecting priorities in distributing supplies when the demand for materials in sales and stock transport orders surpasses the existing inventory or capacity. Through the utilization of selection and exclusion conditions, along with prioritizes, you can automate the rescheduling and redistribution processes in alignment with your company’s strategy. Following this, the Configure BOP Variant application can be employed to create a variant, facilitating the direct execution of the corresponding backorder processing run within the app or through the Schedule BOP Run application. Access to this app is contingent upon the assignment of the Order Fulfillment Manager (R0226) business role to your user account.

Configure Bop Variant

Utilizing this application, you have the capability to establish a variant for backorder processing (BOP), incorporating optional filters and prioritizers. This allows for the automated rescheduling and redistribution of materials in restricted supply. The outcomes of successive backorder processing runs can be viewed in the Monitor BOP Run application.

Configure Custom BOP Sorting

Using this application, you have the capability to generate sequences for prioritizing requirements originating from sales and stock transport documents based on attributes that are not amenable to straightforward alphanumeric sorting, such as customer or sold-to party. In this process, you establish a logical framework for prioritizing requirements, which is subsequently applied in the Configure BOP Segment application and in subsequent backorder processing runs initiated from either the Configure BOP Variant or Schedule BOP Run applications.

Schedule BOP Run & Monitor BOP Run

Using these applications, you can set up and timetable tasks to execute backorder processing (BOP) runs. This involves specifying the technical parameters governing the selection criteria, operational characteristics of the run, and, if necessary, simulative and recurring runs, as well as subsequent update processes and logging. The outcomes of any scheduled run through this app can be monitored in the Monitor BOP Run application.

This concludes this article and the main object of writing this to give you all a high level understanding of Backorder Processing in aATP, SAP S4 HANA. Please do share all your insights.

The post Backorder Processing in aATP – SAP S4 HANA appeared first on ERP Q&A.

After noticing many problems related to credit exposure update that are hard for customers to troubleshoot, I have decided to write this blog to empower customers getting further knowledge in the topic. On this blog, I am going to focus on credit exposure update during creation of a sales order with an item relevant for delivery. The item in the order would have quantity of 1 PC and the price would be of 1 EUR.

The analysis will be from SD perspective. It will be explained steps until the commitments are sent to method IF_UKM_COMMITMENT_PUSH_R3-PUSH_COMMITMENT. The example is meant for SAP Credit Management (FSCM) only.

The system used is an internal SAP system S/4HANA 2021. In the example, credit check will not block the document since it resets the confirmed quantities and then there would be no credit exposure updated as per standard logic.

Before showing the debugging steps, there are some points important to know for analysis that I will mention below.

Important points to know about credit exposure update before debugging:

The structure MCVBEP (internal tables OWL_MCVBEP, XMCVBEP, XMCVBEP_LS) is the one used for passing the credit values of the items in the document to the structures used for updating credit exposure.

The fields to be aware of, for credit exposure analysis, from MCVBEP structure, are the following:

• OEIME: Open delivery quantity
  
• OEIKW: Open delivery credit value
  
• OEIKWGES: Total open delivery credit value (without guarantee)
  
• OEIKWAA : Guaranteed open delivery value

For a document which is not guaranteed by any Payment Guarantee Procedure (Credit card and Letter of credit), OEIKW and OEIKWGES will always have the same value as the system does only support 100% of the values guaranteed or nothing. In the following example, only field OEIKW is relevant.

The standard logic for commitments calculation for a schedule line is the following:

• VBAP-CMPRE * VBEPD-OLFMNG (confirmed quantity not yet delivered)

Credit Management in SD is based on Badi BADI_SD_CM. The Badi can be activated or not.

The credit exposure calculation takes place in method IF_EX_BADI_SD_CM~FSCM_COMMITMENT_UPDATE_ORDER. The standard class is CL_IM_UKM_SD_FSCM_INTEGR1. It may be used a different class if there is a custom implementation of the BADI_SD_CM. The example in this post uses the standard class.

To have the credit exposure updated for a delivery relevant item, it is needed to have confirmed quantity in the schedule lines and some configurations like:

• The item on the sales document needs to be relevant for billing (FKREL). Billing relevance of the item category can be set in transaction VOV7.
  
• For the credit value update of the item the ‘Credit active’ indicator needs to be flagged on the item category in transaction OVA7 or in transaction VOV7. (The setting is also referred to as ‘Active receivable’.)
  
• In the pricing procedure used for pricing, subtotal ‘A’ must be entered in a line for determining the credit value (VBAP-CMPRE). You maintain the credit price in transaction V/08.

Further information about Credit Management configurations can be checked in KBA 2788718.

Checking if the exposure would be correct with the standard class:

Before showing the credit exposure update steps, I would like to demonstrate where in the code it is checked if there is a custom implementation of BADI_SD_CM and how to test the credit exposure update with the standard class to tell if the issue you are facing is because of the custom implementation.

The method FSCM_COMMITMENT_UPDATE_ORDER is the one responsible for sending the commitments. It is called from FM MCV_UPDATE_CM_ORDER. To troubleshoot an error with credit exposure update in a non-production environment, if there is any custom implementation of BADI_SD_CM active, we can change variable BADI_SD_CM_ACTIVE to blank and the update will happen with the standard class CL_IM_UKM_SD_FSCM_INTEGR1. That should be done in update task.

Then if the update is correct, the issue is probably caused by the custom implementation of BADI_SD_CM.

Below are the debugging steps I took to analyze the credit exposure update for the sales order. It is shown the code that is run after saving the order. Later in the blog, I also demonstrate the steps in update task.

Steps for credit exposure update from SD for a sales order with an item relevant for delivery:

Step 1

In the below screenshot, method FSCM_CREDIT_CHECK_ORDER was called during saving of a sales order and we can see that XVBEP-OLFMNG is 1 for one of the schedule lines. So, we can expect the quantity of 1 being used in form CMPRE_CALCULATE to calculate the credit price.

Step 2

In that sales order, only the second schedule line has confirmed quantity. Here we can see that when CMPRE_CALCULATE is performed for that schedule line (OWE_MCVBEP-ETENR = 0002), the open delivery value (OWE_MCVBEP-OEIKW) was calculated as 1.

Step 3

The actual calculation of the commitments happens during method FSCM_COMMITMENT_UPDATE_ORDER. Form CMPRE_CALCULATE will calculate again OWE_MCVBEP-OEIKW, which will send the value to internal variable XMCVBEP_LS-OEIKW in the method.

Step 4

That value from XMCVBEP_LS-OEIKW is sent to the variable LV_OEIKW, which represents the open delivery value from the schedule line that will be sent to the internal tables used to update the credit exposure.

Step 5

During simulation (before commit work), LT_COR_D is the structure used to store the data that represents what would be sent to update the commitments in UKM_ITEM table.

Internal table LT_COR_D should be updated with the credit value from lv_oeikw as per the screenshot below.

Step 6

This is how LT_COR_D looks like at the end of FSCM_COMMITMENT_UPDATE during simulation.

Steps in update task:

Step 7

The same calls to form CMPRE_CALCULATE that happened before update task should happen now as well. That will update variable LV_OEIKW (open delivery value) as in step 4. In the next screenshot, it is shown when LT_COR internal table is updated for the schedule line with the confirmed quantity.

Step 8

Here the data from LT_COR is transferred to LT_COM, which is the table from SD used to send commitments information to method push_commitment.

Step 9

This is how LT_COM should look before being sent to push_commitment. The amount of 1 will be update for the currency of the credit segment.

Step 10

Now the method push_commitment is called. That is the logic from SD side used to update commitments

If the structure LT_COM is correctly sent to push_commitment and still the credit exposure is not correctly updated, then there may be an implementation of badi UKM_FILL active that is changing the credit exposure or there is another issue to be checked with FIN-FSCM-CR side for updating the commitments.

The post Debugging steps of sales order credit exposure update analysis from SD perspective appeared first on ERP Q&A.

Background

In S/4HANA Cloud, the SAP best practice content provided by SAP normally fulfills basic E2E business requirement. Different from S/4HANA On-Prem or S/4HANA Private Cloud where customer has full access to the backend system (e.g. SPRO) to change configuration, customer uses SSCUI apps to change some configuration settings in S/4HANA Cloud. However, most SSCUI settings are only defined in the design time and it is difficult to handle different process variants in Q2C order process.

With help of CPF tool (Configurable Parameters & Formulas), it is possible to define business rules in S/4HANA Cloud to influence different aspects of sales order process at runtime.

SAP Business Rule Framework plus (BRFplus) is widely used in different area of SAP products. There is also possibility to utilize BRF+ to allow customer define flexible business rules via BRF+ in CPF application.

SAP S/4HANA Cloud Private Edition Financials for SAP ERP Certification Preparation Guide

This blog shows CPF usage “S03” to determine pricing date on sales order header based on business rules defined by BRF+.

Business Example

Customer wants to define complex business rules to determine pricing date on sales order header. Comparing with the approach of CPF decision table, customer would like to utilize the capability offered in BRF+ to define business rules. For example, customer can not only define decision tree to influence pricing date, but also write logical expression to determine pricing date.

In this example, I’d like to show detail steps of generating BRF+ application for CPF usage and define business rules via BRF+ to determine pricing date.

Configuration Details

As of now, the BRF+ approach is not ye supported in S/4HANA Cloud. For some CPF usages, the BRF+ option is offered in S/4HANA OP2021. Therefore, I am testing BRF+ features in S/4HANA OP2021 version.

By the way, there is plan to enable BRF+ approach on S/4HANA Cloud. Please stay tuned for new features on S/4HANA Cloud for CPF improvement.

Since customer is able to access IMG on S/4HANA On-Prem, it is possible to access to CPF configuration from IMG.

Create BRF+ Application

Go to following IMG path to create BRF+ application.

System navigates to the BRF+ workbench. Create a new BRF+ application and provide required information.

Save the BRF+ application and activate it.

Keep the BRF+ application like it, do not create BRF+ function now because the BRF+ function and other objects will be generated from CPF later.

Define Factory Calendar Determination Rule

Open following IMG node to define factory calendar determination rule.

Define a factory calendar rule and specify the source priority

Define CPF Parameter Catalogs

Open following IMG node to define parameter catalog for pricing date.

There are some standard parameter catalogs available for CPF usage “S03”. Customer can directly include these parameter catalogs to build up business rules in CPF.

In my example, these standard parameter catalogs are sufficient. But it is still possible to add new parameter catalogs by user, e.g. adding custom fields as available parameter catalog.

Assign BRF+ Application to CPF Usage

Open following IMG node to assign existing BRF+ application to CPF usage. The BRF+ application was already created in previous steps.

It is possible to use search help to find out the BRF+ application.

Save the entry and mark this BRF+ application as default.

Define CPF Formulas with BRF+

Open the following IMG node to define CPF formulas for pricing date determination.

Define a new formula

Select the formula ID and click sub-folder “Assign Formula Parameter” to add parameter catalogs to CPF formula

In this example, sales org, sales office and sales group as selected to build up business rules in CPF.

Double click the sub-folder “Assigned Usage Task” to link BRF+ application to CPF usage task.

The CPF routine “2” represent the BRF+ is used to define business rule. Click the button in left top to generate BRF+ function.

In the pop-up dialog box, name the BRF+ function and click button “Generate and Save”. The BRF+ objects are generated automatically.

Define Business Rules in BRF+

Create the Ruleset in BRF+ function.

Then click button “Create And Navigate To Object” to define rules in rule set.

Create a rules in ruleset based on different sales document types.

In this example, I created two rules for sales order and sales quotation. Navigate to the rule of sales order to create expression.

Create a decision table for sales order and select the columns as below to build up decision table.

Then define the business rules in decision table.

In the business rule, the offset 7 days is defined for sales org 1010/sales office 100/sales group 100 combination, which means when sales org, sales office, and sales group combination in sales order matches CPF rule, pricing date will be determined with +7 days.

Activate the decision table and simulate the business rules. For example, use following input value to simulate business rule defined in BRF+

Execute and display the processing steps

The offset value “7 days” is determined for sales org 1010, sales office 100 and sales group 100.

Define Custom Routines for Pricing Date Determination

Open following IMG node to define custom routine for CPF formula of pricing date determination

Create a new custom routine for pricing date determination

Click the line and double click the sub-folder to assign CPF formula to custom routine.

Assign Custom Routine to Sales Document Type

Open following IMG node to assign custom routine number to sales document type.

The custom routine “3000001” defined in previous step is assigned to sales document type “OR”.

Save the entry.

Test BRF+ Rules in Sales Order

Go to transaction VA01 to create sales order. Provide required information to create a sales order.

Because the business rule defined in BRF+ is not matching, the current date is determined as pricing date.

Go to sales order header to change the sales office to 100 and sales group to 100 which match to business rule defined in BRF+.

After the sales office and sales group are changed, the pricing date is re-determined according to business rule maintained in BRF+. The pricing date is calculated with considering public holiday.

Save the sales order, and calculated pricing date is persistent in sales order.

Create another sales order, make sure the combination of sales office and sales group doesn’t match to business rule defined in BRF+.

The default pricing date is calculated. The business rule defined in BRF+ is not functional here.

The post S/4HANA Q2C Sales Flexibility: Using BRF+ to Determine Pricing Date appeared first on ERP Q&A.

In this blog post I will explain how to configure the Flexible workflows for the Condition Contracts and Settlement documents. The Pre-requisites for understanding this topic are that the SAP Consultants must have basic knowledge of Condition Contracts and Settlement documents in S4HANA.

You can configure and manage workflows for sales rebate processing such as the approval processes for condition contracts and settlement documents and the release of condition contracts for settlement.

Depending on the workflow you want to manage, you open the Manage Workflows for Condition Contracts app or the Manage Workflows for Settlement Documents app.

To create a new workflow, on the Manage Workflows screen, you make sure that the workflow you want to define is selected and then choose Add. You can then define the workflow steps, start conditions, and exception handling.

Manage Workflows for Condition Contracts

With this app, you can manage workflows related to condition contracts, such as condition contract release and condition contract release for settlement.

Manage Workflows for Settlement Documents

With this app, you can manage workflows related to settlement management documents, such as settlement document release.

Condition Contract -> Settlement Release of Condition Contract

• Manage Workflows for Settlement Documents -> Release of Settlement Document

In order to automate processes in Settlement Management with workflows, you first have to make settings in the Manage Teams and Responsibilities app.

Check the transaction SWE2 in SAP GUI if Workflow Linkage is setup

Create Contract Process Variants and assign to Contract Type

Before you can manage workflows for Settlement Management, you need to define condition contract process variants to which you assign contract types.

SPRO->Logistics General -> Settlement Management -> Condition Contract Management -> Condition Contract Maintenance -> Define Condition Contract Process Variants.

Activate Condition Contract Approval Process

SPRO->Logistics General -> Settlement Management -> Condition Contract Management -> Condition Contract Maintenance -> Define Condition Contract types

Disable Automatic Accounting document generation of Settlement document

SPRO->Logistics General -> Settlement Management -> Settlement Documents -> Document Types

Enable Condition contract Event Management

Define Status Groups

SPRO->Logistics General -> Settlement Management -> Settlement Process -> Define Status Groups with Application Statuses

Define Settlement Process Types

SPRO->Logistics General -> Settlement Management -> Settlement Process -> Define Settlement Process Types

Authorizations in Settlement Management

You can implement an authorization check that precedes the creation of accounting (FI) documents to ensure that only designated employees can release settlement management documents to Financial Accounting. This function allows you to meet security and legal requirements.

SPRO -> Logistics – General -> Settlement Management -> Basic Settings -> Specify Extended Scope of Settlement Management.

Authorisation Objects W_WBRK_ORG , W_WBRK_FKA & W_WBRK_STS check for Authorization of users during processing of Settlement Documents created out of Condition Contracts. The access for Release to Accounting and Reversal of Settlement document can be managed with these objects.

Authorisation Objects W_COCO & W_COCO_ORG check for Authorization of users during processing of Settlement Condition Contracts. The access to Release condition Contracts can be managed with these objects.

Once above mentioned setup is in place, you can now proceed to test the end to end workflow process as below.

Open the Condition Contract in change mode and Click on Request Approval and save document.

Release Condition contract from the Workflow approval box.

The condition Contract will now be seen as active.

Open the Condition Contract again in change mode, and Lock Settlement and save document.

Open the Condition Contract again in change mode, and request Settlement Approval and save document.

Release Condition contract for Settlement from the Workflow approval box.

Settle the condition Contract for Delta OR Partial or Final Scenario.

Request for settlement document release via workflow. Go to status and click on “Workflow release required”, assign the status and save document.

Approve Settlement document from the Workflow approval box.

Release the settlement document to accounting.

The post Flexible Workflows in Condition Contract Management appeared first on ERP Q&A.

Introduction

In this Blog post we will explain how to use a new migration app ( Migrate your data app ) using demo system S4hana 2020

SAP MM Certification Preparation Guide

In SAP S/4HANA 2020 and later versions, you need to use Migrate Your Data Fiori App instead of LTMC, you can still use LTMC in S4Hana 2020 but those projects will not be changed using Migrate Your Data app you can only display it.

How to create project using Migrate Your Data app

in our example we will use migrate data using staging table to upload the data using XML file format

Click on create project using staging table

choose you project name and mass transfer ID that will help you later to transfer your project between your clients

then click on step 2

you will be transferring to migration object screen, you need to search for specific object then select it

in my case i will choose open sales order object

select the migration object and click on move bottom to include the object to your project

Note: you can include more than one migration object in your project

then click on review

then below message will appear asking for your permission to add another related object ? in my case I will choose do not add

below screen will show you overview of your project and migration object

click on create project

now your project is created with your migration object and ready to download your template file and proceed to migrate your data

How to create field mapping using download and upload function

in this section we will explain how to map the value you inserted in the XML file with SAP value

click on created project

you will find that there is an open mapping tasks

select the object and click on mapping tasks

here you have 2 options to do mapping, you can download the fields you need to map then edit that field in XML then upload it again or you can do the field mapping directly in the project

now we will see the option of create mapping directly in the project

in our case we need to map the number range for sales order if it external or internal, click on mapping task.

below screen will open, in the left side you will see the mapping task and you can change or confirm it on the right side of the screen.

click on customizing and choose the right mapping as per you requirement

in my case I will select internal numbering

status changed to revised, then confirm to continue

status changed to confirmed

second option is to do mapping using XML file then upload it again with the mapping value

this option will help you to keep all mapping tasks in one file to upload it again in another client

Select mapping task and click on download value then go to monitoring to download the XML file

SAP Fiori Application Developer Certification Preparation Guide

choose mapping project and click on download file

after download the file edit the data in the XML file then upload it again

How to upload your data using XML file

open migrate your data app then select your project as below

click on project name

select your migration object and choose download template

after downloading the template you can open it and fill the data as per your requirement then save the file

and click on upload file

below screen will open > click on upload then choose your file location

wait until uploading is finish, the uploaded file will appear in the below section

then wait until the file is transferred

go back and select simulate

wait until simulation is done, if there is an error you will find it as below

there is an error in task mapping we will map it as we discussed in the previous section in this blog

click on mapping task

SAP S/4HANA Financials Professional Certification Preparation Guide

then map and confirm all tasks as explained in the above section of this blog

after confirming all task needed you can go back and simulate again, you will see that there is no error in simulation

click on migrate to start migrate your data

after completing the migration you will see that your data is migrated successfully

How to transfer your project to another client

Go to source system for example DEV system ( which you create a project on it )

Execute t-code SE38

Execute report /LTB/MC_PROJ_Q2P

click on export, then insert your mass ID you have inserted when you create the project

choose the location to save the project file

Then go to the target system ( for example production system ) and Import the project file that you save earlier

go to Se38 > insert program : /LTB/MC_PROJ_Q2P > execute > then choose import, select an option of local sap s4hana database

then execute and choose the program file you have saved earlier from source system

project will transfer successfully and you can use it in production server

NOTE : instead of using se38 and execute the program, you can do the same from LTMOM it will transfer you to the program directly to export and import your project

how to move your project between clients

you have an option in LTMOM to move the project from client to another client, for example you want to move you project from DEV 100 to DEV 110, this option will help you do that and remove the project from DEV 100

Go to T-code: LTMOM in target client > choose your project > Go to > use project in different client

then execute

below screen will open, click on continue

the project will be moved from the source client to the target client

Important information for production system ( non modifiable system )

It is not possible to create or modify projects in production system. You cannot, for example, remove a migration object. If you need to make such changes, you can change the project in the source system and transfer it again to the target, creation option will not be available in production system

Example: You transfer a project that contains migration objects A, B, and C to the target system. In the source system you remove object C. You transfer the project again to the target. The project in the target system will now contain objects A and B only.

below screen from production system, as you see there is no option to create a new project

SAP S/4HANA Cloud Private Edition Central Finance Certification Preparation Guide

Additional Information for non-Production Systems

You can create and modify projects in any system that is not a production system. If you add an object in the target system, it will not be removed if you transfer the project again.

Example: You create a project with migration objects A, B, and C. You transfer this project to a non-production target system. In the target system, you add object D. The project in the target system contains objects A, B, C, and D. In the source system, you remove object C, and then transfer the project again to the target system. The project in the target system now contains object A, B, and D.

below screen from non production system ( DEV ), as you see there is no option to create a new project

The post Full guide and answers for using migrate your data app in S4hana 2020 appeared first on ERP Q&A.

In this blog post I am going to talk about SAP Fiori Apps for Reporting/Analysis in the area of Sales.

SAP Sales Cloud Version 2 Implementation Consultant Certification Preparation Guide

Introduction

SAP Fiori Apps is a group of accumulated cards of Apps, which represents the new user experience that assures that employees’ and managers have consistent, coherent, simple, and intuitive user experience.

The SAP Fiori Library is constantly expanding for both SAP S/4HANA on-premises and SAP S/4HANA cloud. The apps run on browser and work seamlessly on smart phone, tablet, and desktop. As a business process owner is requested to permanently improve the user experience. SAP S/4 Projects will use SAP Fiori and it is so different from the SAP ECC.

Objectives

• Gain an overview of SAP Reporting/Analytics Apps for Sales
  
• Explaining and presenting the basics of the most important SAP Reporting/Analytics Apps for Sales
  
• Make you familiar with the most important Apps that will help you to complete the business processes.

Main Part

I will bring to light the most important SAP Fiori Apps that can be used for Analysis / Reports for Sales and Distribution, I will explain in detail about their uses and scope. Let’s see below more details.

---

The first app mentioned in this list is My Sales Overview, which provides information such as sales order data, performance figures, and quick actions using actionable cards in a dashboard format. An internal sales representative can use the app to search for, create, modify, or view sales information to improve reaction time and allows the user to act on the most important issues first.g

1. My Sales Overview, App ID F2200

Application Type	Analytical (SAP Fiori elements: Overview Page)
Form Factor	Desktop, Tablet

• Cards included in this app provide information on sales data, including open sales quotations and sales orders, blocked credit memo requests, customer returns, and customer information.
  
• Cards are displayed based on the roles assigned to your user and you can select which cards to display under Manage Cards in your user settings.
  
• You can filter the data displayed in the cards in one of the following ways:
  
  • Specify default sales area filters (Sales Org., Distr. Channel, and Division) under Default Values in your user settings.
    
  • Specify filter values in the filter bar of the My Sales Overview app.

My Sales Overview Cards

Card	Description
Customer Contacts	Displays a list of customer contacts, sorted by customer classification and customer. Direct access to the Customer – 360° View application by clicking on the customer’s name and allows you to display contact information for the customer by clicking on the customer contact link.
Open Sales Orders	Displays a list of sales orders that are still open and require processing, starting with the most recently changed or created sales orders. Direct access to navigate to the Manage Sales Orders app by clicking on the card header and allows you to display details of a sales order by clicking on it.
Customer Returns	Displays a list of customer returns, starting with the most recently changed or created customer returns and allows you to display details of a customer return by clicking on it. Permission to filter the displayed customer returns by status (the default is Active Returns). Direct access to the Manage Customer Returns app by clicking on the card header.
Blocked Credit Memo Requests	Displays a list of credit memo requests that are blocked for checking, starting with the most recently changed or created requests. Direct access to the Manage Credit Memo Requests app by clicking on the card header and allows you to display details of a credit memo request by clicking on it.
Open Sales Quotations	Displays a list of sales quotations that are incomplete, starting with the most recently changed or created quotations. Direct access to the Manage Sales Quotations app by clicking on the card header and allows you to display details of an open quotation by clicking on it.
Quick Actions	Provides shortcuts for creating sales documents, including: Sales Orders Sales Quotations Credit Memo Requests Customer Returns
Incoming Sales Orders	Allows you to select the length of the analysis period. By default, the last four months are considered as the current period. Displays a monthly comparison of incoming sales orders between the Current Period and the Previous Period, that is, the same period one year ago. Direct access to the Incoming Sales Orders – Flexible Analysis app by clicking on the graph. The user’s currency is derived from the company code to which they belong.
Sales Quotation Pipeline	Displays sales quotations grouped by their expiry timelines. Direct access to the Manage Sales Quotations app by clicking on the card header and allows you to display quotations by clicking on their group.
Sales Order Fulfilment – Monitor Issues	Provides an overview of sales order fulfillment issues and allows you to display sales orders with fulfillment issues by clicking on the issue type. Direct access to the Sales Order Fulfillment – Resolve Issues app by clicking on the card header.

The second app that I will mention in this list is Sales Management Overview, as a sales manager role you can get a graphical overview of various sales data on analytical cards. Using this app, you can gain comprehensive insights into your current sales situation and respond quickly.

2. Sales Management Overview, App ID F2601

Application Type	Analytical (SAP Fiori elements: Overview Page)
Form Factor	Desktop, Tablet

Key Features

• Each sales topic is represented by a card. On the cards, you can view relevant sales KPIs
  
• Sales data is visualized in charts and lists
  
• You can filter results by various criteria, such as sold-to party and sales organization
  
• You can specify a preferred currency for displaying the results
  
• You can navigate to related apps to drill down into the data

The app provides the following cards:

Card	Description
Incoming Sales Orders	Indicates the total net value or the number of sales order items that are relevant for billing or delivery Displays the last four months and lets you compare them to the same period in the previous year Direct access to the Incoming Sales Orders – Flexible Analysis app for more details
Customer Returns	Indicates the total net value of customer return items that are relevant for billing or delivery Displays the last four months and lets you compare them to the same period in the previous year Direct access to the Customer Returns – Flexible Analysis app
Incomplete Sales Documents	Displays the total number of incomplete sales documents Displays the number of incomplete sales documents by document category as a percentage Direct access to the List Incomplete Sales Documents app to view the document and complete the data
Backorder Items	Displays the total number of backorder items Displays the four plants with the most backorder items Direct access to the Sales Volume – Backorders app for more details
Profit Margin	Indicates the difference between sales volume and costs Displays the sales volumes for the last four months and lets you compare them to their profit margins Direct access to the Sales Volume – Profit Margin app for more details
Blocked Sales Orders	Displays the total net value and the number of blocked sales orders by issue type Direct access to the Sales Order Fulfillment – Analyze Issues app for more details
Overdue Sales Orders	Displays the total net value and the number of overdue sales orders by issue type Direct access to the Sales Order Fulfillment – Analyze Issues app for more details

The next Fiori App I will talk about is Sales Performance – Plan/Actual. With this app, you can compare planned and actual sales on different dimensions, such as sales organization, customer, and material. By doing so, you can analyze to what extent your sales targets are being achieved and thus gain insights into your current sales performance.

3. Sales Performance – Plan/Actual, App ID F2941

Application Type	Analytical (SAP Fiori elements)
Form Factor	Desktop, Tablet

You can select value plans to compare the planned and actual sales values.

After a value plan is selected, the plan and actual data are compared as follows:

• Planned and actual values represent either incoming sales orders or sales volume, depending on what you have planned in the selected sales plan version
  
• Planned and actual values are compared by month, quarter, or year within the planned period, depending on how you have defined this in the selected sales plan version

You can display a hybrid view that visualizes the differences on a chart while displaying the details in a table. In addition, you can compare the planned sales volume to the actual net sales volume (sales volume minus credit memos).

You can drill down to further compare the plan and actual data. The drill-downs available to you are the dimensions that you have defined for the sales plan version.

You can select relevant data (for example, specific customers) from the chart and then navigate to related apps to show quotation conversion rates, contract fulfillment rates, and check open sales.

You can select quantity plans to compare the planned and actual quantities (Sales Performance – Plan/Actual – Quantity-Based). Planned and actual quantities represent either incoming sales orders quantity or sales volume quantity, depending on what you have planned in the selected quantity plan

The next Fiori App is Customers Overview. With this app, you can get an overview of the sales data of one or more customers.

4. Customers Overview, App ID F4645

Application Type	Analytical (SAP Fiori elements)
Form Factor	Desktop, Smartphone, Tablet

You can use this app to:

• View various sales measures of customers represented by cards. The data is displayed in an easy-to-consume manner using charts and lists.
  
• Filter results by various criteria, such as sold-to party, sales organization, sales group, and so on.
  
• Specify a preferred currency for displaying the results. You must select the display currency and at least one sold-to party (customer) in order to see the corresponding sales data.
  
• Navigate to the related apps to drill down into the data.

The app displays the following cards:

Card	Description
Frequency of Sales Orders	Displays the average number of sales orders per month for the last 6 months. Displays the number of sales orders per month for the last 6 months in a chart. Direct access to the Manage Sales Orders app.
Incoming Sales Orders	Displays the average net value of sales orders per month for the last 6 months. Displays the net value of sales orders per month for the last 6 months in a chart. Direct access to the Manage Sales Orders app.
Open Sales Orders	Displays the list of sales orders that are not completed. This status is based on the Overall Status filter in the Manage Sales Orders app. The sales orders displayed are ordered by the requested delivery date. Direct access to the Manage Sales Orders app.
Rejected Sales Orders	Displays the total number of sales orders that are either partially rejected or fully rejected (Everything Rejected). This status is based on the Rejection Status filter in the Manage Sales Orders app. The data displayed in this card is only for the sales orders from the current year. Displays the number of partially rejected sales orders. Partially rejected sales orders are those where only some of its items are rejected. Displays the number of fully rejected sales orders. Fully rejected sales orders are those where all its items are rejected. Direct access to the Manage Sales Orders app.
Customer Returns	Displays the total number of items returned by customers for various reasons. The data displayed in this card is only for the items returned in the current year. Displays the number of items returned by customers for each reason. The reasons are ordered in the descending order of the number of items tagged against it. Direct access to the Customer Returns – Return Rate app.
Delivery Performance	Displays the delivery performance of sales orders over the last 6 quarters. Displays the quarterly data in a chart for the following key figures: Delivered as Requested: Includes sales order items that have been delivered by the customer’s requested delivery date. Delivered as Committed: Includes sales order items that have been delivered by the committed delivery date.
Sales Volume / Profit Margin	Displays the sales volume against profit margin for the last 6 quarters in a chart. Direct access to the Sales Volume – Profit Margin app.
Sales Volume by Sales Area	Displays the net sales volume from all sales areas, which are assigned to the selected sold-to party, for the current year. A sales area is a combination of sales organization, distribution channel, and division. Displays the sales volume in each sales area, assigned to the selected sold-to party, for the current year in a chart. Direct access to the Sales Volume – Check Open Sales app.
Open Quotations	Displays the list of sales quotations that are not completed. This status is based on the Overall Status filter in the Manage Sales Quotations app. The sales quotations displayed are ordered by their validity. Direct access to the Manage Sales Quotations app by clicking on the card header to see details of all the open sales quotations. Allows you to navigate to the fact sheet of a specific sales quotation by clicking on it.

The next Fiori App is Customer Returns – Flexible Analysis. With this app, you can analyze the monthly rolling trend of your customer returns based on flexible combinations of dimensions.

5. Customer Returns – Flexible Analysis, App ID F3889

Application Type	Analytical, BW Query used (SAP Fiori: Design Studio)
Form Factor	Desktop

Provide the following KPIs for analyzing customer returns:

• Customer Returns: Net amount of customer return items that are relevant for delivery or billing
  
• Return Item Quantity: Quantity of customer return items that are relevant for delivery or billing
  
• No. of Return Items: Number of customer return items that are relevant for delivery or billing
  
• Analyze the return rate of incoming sales orders
  
• Analyze customer returns by return reason
  
• Drill down further into a list of customer return items

The app Order-to-Cash Performance – Overview enables process managers and process owners to get a quick overview of issues and the current and past performance of the order-to-cash process without having to open many different reports and transactions. All relevant information is shown on a single page in an attractive and efficient way.

6. Order-to-Cash Performance – Overview, App ID F2242

Application Type	Analytical Analytical (SAP Fiori elements: Overview Page)
Form Factor	Desktop, Tablet

Activities you can perform with the help of the app:

• Track delivery blocks or billing blocks
  
• Detect changes made to critical fields of a sales order
  
• Monitor lead times (for example, order to delivery or goods issue to billing)

The overview page enables process managers and process owners to get a quick overview of issues, and the current and past performance of the order-to-cash process without having to open many different reports and transactions. All relevant information is shown on a single page, which is visualized using cards for multiple types of content. On clicking a card all relevant data is displayed. You can use the interval drop-down to view data for a different time range.

Further, the app that I am going to talk about is Sales Volume – Check Open Sales, with which you can check sales volume in comparison with previous months, with the additional insight of open orders and open deliveries for the current month, in comparison with previous months. The app enables you to see briefly how the current month’s sales volume relates to the previous month and helps you to identify where you can take action in order to increase your sales volume.

7. Sales Volume – Check Open Sales, App ID F2270

Application Type	Analytical (SAP Fiori: SAP Smart Business generic drill down app)
Form Factor	Desktop, Tablet

You can use the app to do the following:

• Filter according to various criteria, such as sales organization, month of billing or year of billing, sold-to party, product, sales document, and so on
  
• Display and analyze the key figures as a chart or a table
  
• Drill down to view detailed information for selected sales organizations, products, sales documents, customer group, sold-to parties, and so on.
  
• Navigate to the object pages (for example, for customer, various sales documents, and product) for further information
  
• Navigate to related apps via the mini tiles at the top of the screen
  
• Navigate to the Sales Order Fulfillment – Analyze and Resolve Issues app

The app uses the following key figures:

Key Figure	Description
Sales Volume	The total invoiced sales achieved during a specified period. This is based on invoice items or debit memo items (debits) that have not been canceled.
Credit Memos	The total amount of credit memos during a specified period. This is based on credit memo items (credits) that have not been canceled.
Profit Margin	The difference between sales volume and costs
Credit Memo Profit Margin	The difference between credit memos and costs
Net Sales Volume	Sales volume minus credit memos
Net Profit Margin	Profit margin minus credit memo profit margin
Net Sales Cost	Costs of sales volume minus costs of credit memos The following are some examples of possible sales processes: 1. Sell-from-Stock: In this case, the cost is usually taken from a condition, which is filled from the material valuation in the product master or, in the case of billing, the goods issue. 2. Third-Party: In this case, the cost is usually taken from a condition, which is filled from the material valuation in the product master or, in the case of billing, the invoice receipt. 3. Intercompany: In this case, the cost is usually taken from a condition record of an intercompany price.
Open Orders	Confirmed sales orders for which a delivery document has not yet been created in the period of the planned billing date (goods issue date). In this case, the net amount of the confirmed schedule lines is shown. In the case of unconfirmed or partially unconfirmed sales orders, the net amount of the not yet confirmed requested schedule line is shown, and the billing date defines the analysis period, for example, month, in which the schedule line is displayed. Scheduling agreements with release are not considered in the calculation of open orders.
Open Billing Requests	Sales documents which are relevant for invoicing, but which have not yet been invoiced in the context of debit memos, for example, debit memo requests or sales orders with billing plans
Open Credit Memo Requests	Returns or credit memo requests for order-related invoicing which have not yet been invoiced
Overall Open Orders	Orders that have been confirmed for delivery, but for which a delivery document has not yet been created (Open Orders), orders which are relevant for invoicing but have not been fully invoiced (Open Billing Requests), or orders which include a billing plan, but in which a customer invoice has not yet been created in the period of the planned billing dates (Open Orders for Billing Plans)
Open Deliveries	Deliveries in which a delivery quantity is not fully invoiced
Deliveries Shipped But Not Invoiced	Deliveries in which a goods issue is posted, but not fully invoiced

The app Sales Volume – Flexible Analysis can be used to gain an understanding of the monthly sales volume.

8. Sales Volume – Flexible Analysis, App ID F1250

Application Type	Web Dynpro
Form Factor	Desktop

Key Features

• You can view the key figures as a graphic or a table on a monthly basis.
  
• You can drill down to view detailed information for selected sales organizations, sold-to parties, bill-to parties, and so on.
  
• You can filter the items according to various criteria, such as year/month, sales organization, sold-to party, and bill-to party.
  
• You can change the displayed ID or description.
  
• You can save your selection as a variant.

The app provides the following key figures:

Key Figure	Description
Net Value	The total net value of items in billing documents
Sales Volume	The total invoiced sales achieved during a specified period. This is based on invoice items or debit memo items (debits) that have not been canceled.
Sales Volume Qty	The total quantity of invoice items or debit memo items (debits) that have not been canceled
Cancellations	Canceled sales volume. Cancellation documents are not considered at all.
Profit Margin	The difference between sales volume and costs
Credit Memos	Net value of items in credit memos. This is based on credit memos that have not been canceled.
Credit Memo Profit Margin	The difference between credit memos and costs
Net Sales Volume	Sales volume minus credit memos
Net Profit Margin	Profit margin minus credit memo profit margin
Net Sales Cost	Costs of sales volume minus costs of credit memos

The next Fiori App is Incoming Sales Orders – Flexible Analysis. With this app, you can use this app to gain an understanding of the monthly rolling trend of incoming sales orders.

9. Incoming Sales Orders – Flexible Analysis, App ID F1249

Application Type	Analytical (SAP Fiori elements)
Form Factor	Desktop, Phone, Tablet

Key Features

• You can view the monthly rolling trend for sales as a graphic or a table.
  
• You can analyze the net values of aggregated sales order items with the display currency.
  
• You can drill down to view detailed information for selected sales organizations, products, product groups, sold-to parties, sales document types, and so on.

Example: You can select the sales document type for a drilldown so that you can compare the incoming sales orders in the available scenarios.

• You can filter the items according to various criteria, such as year, month, sales organization, product group, and sold-to party.
  
• You can change the displayed ID or description.
  
• You can save your selection as a variant.

The post List with 9 SAP S/4 HANA Fiori Apps for Analysis and Reports | SALES (SD) appeared first on ERP Q&A.

Attribute view:

Attribute views are dimensions, BW characteristics or master data.

Attribute views are used to join to a dimension or attribute view.

In most cases used to model master data like entities (like product, employee, business partner)

Highly re-used and shared in analytic and calculation views

SAP S/4HANA Management Accounting Certification Preparation Guide

How to create attribute view with customer:

Go to remote desktop connection < start < click on HANA studio

How to create an attribute view:

Right click on sub package<new<click on attribute view

Provide name AT_MATERIAL<provide label<select subtype as standard <click finish

Click on plus icon<select objects

Select table MARA<click ok

Select required output columns

Again click on plus icon <add table MAKT<click ok

Join MARA MATNR to MAKT MATNR

Join type as text join<language column as spras

Join type:

Text join: text join is used to fetch the description based on user’s session language. Once we implement the text join in sap HANA, it automatically finds out user’s language and gives description in that language.

Select MAKTX as output column

Click on semantics<provide MATNR as key attribute

Key attribute is a kind of primary key for the attribute view. But, it doesn’t prevent the passage of duplicate values. It is basically needed to determine the join execution order at the run time when multiple tables are used in an attribute view.

In attribute views there is one mandatory step. Whatever keys in the table one key we need to define inside an attribute view

Provide label mapping

Label mapping:

We can choose to associate an attribute with another attribute description. Label

Mapping is also called as description mapping. For example if a1 has a label column

B1, then you can rename b1 to a1.description. The related columns appear side by

Side during data preview

Click save and validate<click save and activate

<assign an object<click finish

Use of assign object: in the select change dialog, either create a new id or select an existing change id that you want to use to assign your change

Click on data preview

Click on raw data<to get output

Output in different language:

Go to best system<right click on system<click on properties

Click additional properties<select locale<click apply<click ok

Click save and validate<click save and activate<click on data preview<click on raw data

The post Implementing attribute view with material appeared first on ERP Q&A.

Since beginning of Covid situation Retail industry is just experiencing a very fast pacing revolution where Customer is as always in the center point of the business process but as well in different physical locations. That means that some of shopping bags are filled in the brick and mortar store and some of them are just a virtual basket.

SAP IBP Certification Preparation Guide

The challenge in this environment is always to keep prices and promotions in sync through all different shopping areas. With rather simple pricing where prices are managed in a master system, let’s assume S/4 Retail then distributed to different systems either via Idoc (in standard COND_A) or to POS system via assortment list, it seems to be straight forward. As a cherry on the cake recently we implemented a solution where the external system was calling pricing on S/4 to calculate prices, subtotals and it was working really well. I can only assume that reason of it could be that SAP is has improved module PRICING (including option to call module for number of articles PRICING_MULTI_ITEM) or we have had a really good developer who did a complex design and build of the solution.

The scenario where there is a new promotional price or simple discount out of regular price as described looks rather no normal to handle. The real problem is coming when you hear from the Customer “we have as well promotion Buy 2 get 3 half price” and this needs to be available for Customers using POS and any virtual basket (web, application etc). For POS system you can almost automatically think about bonus buys available in Retail system which is a good direction. In transaction RDMBBY01 you simple maintain data as an example for buy 2 get 3 half price.

User interface is not the newest one but it works and I have to admit it’s straight forward. Stored bonus buy is then distributed to POS but unfortunately in case of integration with sap pricing procedure it’s not so easy anymore. For any external receiving system some integration logic needs to be built but in case of integration with f.ex pricing used in Sales orders in Retail there is no easy way to integrate it, besides implementing your own logic using sale condition grouping calculation or free items but sooner or later you will find out that this solution is simply saying very heavy to extend and maintain.

Theory

As the new is always coming and SAP has decided to solve this issue with a central repository for pricing and promotion via tool SAP Omnichannel Promotion Pricing (OPP). In theory OPP is a central tool to store prices and promotions across channels and use to either calculate sales price per request or distribute it to relevant application.

Inputs

With definition of OPP that is a central tool for prices and promotion with function of either calculation of price or distribution to relevant systems to keep this area in sync throughout the landscape. For this purpose, as a input for the system following is needed:

• Regular price – this price is not set in OPP but usually is distributed from your backend system (S/4 or ECC) via DRF or imported to SAP CAR from external system as well via DRF inbound functions on CAR.
  
• In case of technical aspect, Sales price is integrated from S/4 as a PSPR or PMPL (includes valuation price) DRF object and Purchase price as PSOS. Then on CAR respectively processing of Product Location and Transportation Line objects are launched.
  
• Offer/Promotion – Offers are created either in Fiori app Manage Promotional Offers or simply imported from backend systems like S/4 (objects n S/4 are Promotions or Bonus Buys) or external systems in both cases via DRF tool.
  
• In case of technical aspects Offers are stored in table /DMF/OFR_TRM_PRD for items details and later on are converted to Promotions that follow format of Association for Retail Technology Standards (ARTS) stored in table /ROP/PROMOTION. To import offer from external system, use DRF function of /DMF/OPIF_OFFER_INBOUND in SAP CAR. In S/4 integration can be done via DRF with objects POFF and PBBY respectively for Promotion and Bonus buy.

What you can see so far, for the integration with SAP backend system Demand Data Foundation (DDF) would be really appreciated. For a kind of simple workaround, would be calling function module for respective objects processing in CAR as it’s in case of external tool integration, but it’s not going to be so smooth like in case of use DDF.

Calculation location option.

What is very powerful from OPP perspective it’s a place where the calculation is taking place. In the past it was always a hiccup at backend if you have had to integrate promotions with sales order (possible via sales conditions) but bonus buys created in backend system and integrated into sales process was nearly not possible. I assume this was one of the reasons why with the OPP you have two options for deployment of this tool.

Central deployment – with this option webservice is residing at CAR system (more preciously I assume it’s kind of java bean). This service is taking regular price, and all offers residing in CAR system and calculates required figures. Nice thing about it is the smooth integration into pricing on you SAP backend. At S/4 side configuration includes setting up RFC connection to service followed by step of setting up what should be sent out and received from service.

What you can see above, towards PPS (Promotion Pricing Service) you can send regular price as a baseline for calculation (I assume f.ex for transaction level discounts) and as a response receive aggregated figures about discount or individual promotions. To receive individual promotions or to limit the results you can use filters and map it into individual conditions in pricing procedure of backend. To trigger calculation at PPS service, routing 317 – OPP: call PPS needs to be assigned to condition in pricing procedure at backend. To achive higher level of flexibility inside routine number of BADIs are available for enhancements.

Entire configuration at S/4 system is done in SPRO -> Logistics General -> Retail: Omnichannel Promotion Pricing (OPP).

Local deployment – with this option of processing, calculation logic of discounts and final sales price is moved to external system. For this reason SAP CAR distributes two types of Idocs via DRF to target system.

• Regular price – with the DRF outbound implementation ROP_PRICE system generates Idoc type /ROP/BASE_PRICE01 with grouped locations for same price and with all price intervals.
  
• Promotions – using DRF outbound implementation ROP_PROMO system sends out standard promotion Idoc /ROP/PROMOTION02 to target system.

Not bonus buy any more in backend but offer in OPP

With the introduction of OPP new Fiori application has been launched to create offer in SAP CAR. As already mentioned, offers can be created either in OPP or they can be imported into system via DRF.

Below are presented couple of examples of OPP offer created with new Fiori app “Manage Promotional Offers” which has similar functionality as part of SAP Promotion Management (SAP PMR).

Every Offer will require couple of header information like a offer name, location where is valid, validity period. On top of it you can assign as an extra information about offer set (grouping purpose) and leading category of products (merchandise category or article hierarchy node) but this is only for reporting purpose. Interesting options compering to backend bonus buy processing is option to create promotion not only for a full day but also happy hours form is available and option to decide if offer is valid only in case non other discount applied so far during processing – Regular Price Only checkbox.

• Buy 3 get 1 for free – typical promotion

Beside the data filled at the level of header of the offer core processing information are enclosed in terms section. What is really nice comparing to backend bonus buy is a usage of term style as a predefined set of fields that user needs to fill in to achieve business logic.

In below example of defined term style for a promotion buy X units get 1 PC for free.

Typical offer similar to bonus buys at backend has two sections buy and get, which conditions that customer needs to fulfill on buy side to be granted with rewards at get side. Important part of each offer is a dimension field that describes which level is taken into account for each side. Possible values:

To reach example with buy 3 get 1 for free, if promotion is on group of products (f.ex same product different tastes) then dimension of product group would be useful and quantity on buy side and similar settings on get side.

• Transaction more then 100 Eur 5% off on total

Another very often promo type is to reach some level of transaction then Customer is receiving either something for free or some discount on total. In below case buy side has dimension of transaction and get side percentage discount on total.

• Buy 3 PC from one group and get 5% discount on products from the other product group

This example shows combination of two conditions at buy side like buy at least 3 PC from current collection to get an extra discount on winter collection.

Each offer initially is stored in tables /DMF/OFR* and then when activated it’s converted to promotion object stored in table /ROP/PROMOTION.

With couples of the OPP examples it’s not possible to explain all useful features of new software. Good thing about all new functionalities residing on CAR is fact that plenty of BADIs are available so custom logic can be built as not all parameters are visible to user in Fiori app. Pay attention to dedicated BADI triggered during conversion of offer to promotion and two fields:

• Sequence – sequence number can be used to describe order with which promotions are applied in target system.
  
• Exclusiveness – could be use in target system to discontinue other promotions from being processed if one with promotion is reached.

The post SAP CAR OPP – Omnichannel Promotion Pricing appeared first on ERP Q&A.

In this blog, I am sharing basic overview of Implementing attribute view with customer

Attribute view:

• Attribute views are dimensions
  
• Attribute views are used to join to a dimension or attribute view.
  
• In most cases used to model master data like entities (like product, employee, business partner)
  
• Highly re-used and shared in analytic- and calculation views

How to create attribute view with customer:

SAP S/4HANA Cloud Private Edition Financials for SAP ERP Certification Preparation Guide

Go to remote desktop connection<start<click on Sap Hana studio

How to create a package:

Expand best system<right click on content<new<click on package

Provide name<provide description<click ok

How to create a sub package:

Right click on package<new<click on package

Provide name as SD <provide description <click ok

How to create an attribute view:

Right click on sub package<new<click on attribute view

Provide name AT_CUSTOMER<provide label<select subtype as standard <click finish

Click on plus icon to add objects

Search for table KNA1<click on table<click ok

Select required output columns

Again click on plus icon<enter table T005T<click ok

Connect KNA1 LAND1 to T005T LAND1 to get output as LANDX <select LANDX as output coloumn

Join type as text join<language as SPRAS

Text Join: text join is used to fetch the description based on user’s session language. Once we implement the text join in Sap Hana, it automatically finds out user’s language and gives description in that language.

Again click on plus object<select T005U table<click ok

Join KNA1 LAND1 to T005U LAND1 because regions are specified with country

Join type as text join <language as SPRAS

Join KNA1 REGIO to T005U BLAND<select output column as BEZEI

Join type as text join <language as SPRAS

Click on semantics<select key attribute as KUNNR

Key attributes:

Key attribute is a kind of primary key for the attribute view. But, it doesn’t prevent the

Passage of duplicate values. It is basically needed to determine the join execution order

At the run time when multiple tables are used in an attribute view.

In attribute views there is one mandatory step. Whatever keys in the table one key?

We need to define inside an attribute view

Provide label mapping

Label mapping:

We can choose to associate an attribute with another attribute description. Label

Mapping is also called as description mapping. For example if a1 has a label column

B1, then you can rename b1 to a1.description. The related columns appear side by

Side during data preview

Click save and validate<click save and activate

<assign an object<click finish

Use of assign object: in the select change dialog, either create a new id or select an existing change id that you want to use to assign your change

Click on data preview

Click raw data<to get output

Output in different language:

Go to best system<right click on system<click on properties

Click additional properties<select locale<click apply<click ok

Click save and validate<click save and activate<click on data preview<click on raw data

The post Implementing attribute view with customer appeared first on ERP Q&A.