SAP S/4HANA Advanced Available-to-Promise (aATP) is a critical component of the S/4HANA suite that enhances the standard ATP (Available-to-Promise) functionality with more advanced and flexible features. It is designed to meet complex order fulfilment processes and ensure higher accuracy and efficiency in inventory allocation and customer order management.

Key Features and Functionalities of aATP

Product Allocation (PAL)

Product Allocation (PAL) in SAP S/4HANA’s Advanced Available-to-Promise (aATP) is a feature that enables businesses to control the distribution of limited products or resources across various customers, channels, or regions. It ensures that constrained products are allocated according to established rules and priorities, preventing overselling and ensuring that key customers or markets receive an appropriate share.

• Purpose: Ensures products are distributed according to predefined rules and limits, preventing overselling and prioritizing important customers or channels.
  
• Process: During order processing, the system verifies these allocations to determine the amount of product that can be confirmed for each customer.
  
• Benefits: Aids in managing limited products, balancing supply and demand, and safeguarding key customer relationships.

In aATP following aaps are applicable for product allocation –

• Configure Product Allocation
  
• Manage Product Allocation Planning Data
  
• Manage Product Allocation Sequences
  
• Assign Product to Product Allocation
  
• Product Allocation Overview

Concepts of Product Allocation (PAL)

1. Product Allocation Object (PAO) steps

• The core of PAL is the Product Allocation Object (PAO), which defines the framework and scope for allocation. It includes relevant materials (products), customers, customer groups, and parameters such as sales organizations or regions.
  
• A PAO simplifies the grouping and management of allocation rules.
  
• The Configure Product Allocation app is used to set up a PAO, allowing you to incorporate various characteristics into the product allocation object.
  
• The first step involves defining allocation rules within the PAO, which includes establishing relevant dimensions (such as products, customers, and regions) and assigning quotas. Allocation rules are time-phased, meaning they can vary across different periods (e.g., weekly, monthly).

Example Scenario

Imagine a company that manufactures a highly demanded mobile phone but has limited production capacity. The company has key customers across various regions and wants to ensure fair distribution to each region. To achieve this, the company creates a Product Allocation Object with rules that allocate specific quantities to each region based on historical sales data and strategic priorities.

Order processing: When orders are placed from different regions, the system checks the available allocation for each region before confirming the order. If a region’s quota is exhausted, no additional orders from that region will be confirmed unless the allocation is increased or unused quotas from other regions are available for redistribution.

In this example, instead of using regions, the allocation is based on a combination of sales organizations and sold-to parties.

Created product allocation objects –

With required characteristics –

2. Product allocation sequence

In our example Mobile allocation sequence consists of two sequence groups in a specific order. This order ensures that we first attempt to fulfil the requested quantity from the specific allocation per customer. If the allocation quantity is insufficient, the system will then use the second allocation during the Available-to-Promise (ATP) check. Consequently, important customers have access to two pools, while other customers can only use the quantity from the general pool.

The capacity sequence section contains a single sequence group that represents transport capacity. This group includes two allocation objects—one for the trailer and one for the battery. During the ATP check, all constraints within a sequence group are considered using AND logic.

3. Allocation planning

• Allocation rules are the core of PAL, determining how much of a product can be allocated to different customers or groups. Quotas are set based on historical data, forecasts, or strategic priorities.
  
• These rules can be time-dependent, allowing businesses to adjust allocations based on seasonal demand or other factors as per their business relevancy.
  
• For this ‘Manage Product allocation Planning data’ app is available where we can allocate the quantity.

Creation of Product allocation objects –

Planning data to be setup for each allocation object –

MOBILE_STANDARD_SALES

Capacity Sequence is nothing but the available capacity –

Planning data setup for MOBILE_TRANS_CAPACITY –

4. Assign product to Product allocation –

Product allocation output

Sales order creation to check confirm quantity after PAL set up. As per below scenario even though my capacity is 30 system has considered 15 qty after considering sequence and planning data by considering current period.

The actual ATP quantity is 100 in the system but system is showing confirm quantity in sales order after Product allocation setup,

5. Product allocation overview app–

This will give end to end overview of product allocation and order confirmation.

Integration with Other aATP Features

• Backorder Processing (BOP): PAL works in conjunction with BOP to reallocate inventory to high-priority orders if the allocations allow.
  
• Supply Protection: PAL can be used in combination with supply protection to reserve inventory for specific customer segments or markets, ensuring that critical orders are always fulfilled.

Benefits of Product Allocation (PAL)

1. Prioritization of Key Customers: PAL ensures that key customers or markets receive the products they need, even in situations of limited supply.
   
2. Controlled Distribution: Prevents overselling by enforcing quotas and ensuring that sales commitments are within the limits of available resources.
   
3. Flexibility and Responsiveness: Time-dependent allocation rules allow businesses to adjust to changing market conditions, seasonal demand, or strategic priorities.
   
4. Improved Decision-Making: Real-time tracking of allocation consumption provides actionable insights for sales and operations teams, enabling better decision-making.

The post Advanced Available – to – Promise (aATP in S/4HANA) appeared first on ERP Q&A.

Milestone billing means distributing the total amount to be billed over multiple billing dates in the billing plan. This approach is particularly beneficial for industries such as engineering, construction & professional services where projects are linked to project completion phases.

Business Example:

Engineering firm such as Windmill Manufacturing company uses milestone billing as follow,

1. Contract Phase – 30%
   
2. Design Phase – 40%
   
3. Assembly Phase – 20%
   
4. Final Invoice Delivery Phase -10 %

At each milestone Billing date Invoice triggers to the Client.

Below are the Configuration steps for Milestone Billing in SAP S/4HANA:

1. We need to Define Billing Plan Type in SPRO/ Transaction Code: OVBO.
2. Define Date Description in SPRO/ Transaction code: OVB0: As per Business requirement create Date description such as- Contract phase, Design phase, Assembly phase, Final Invoice phase.
3. Define and Assign Date Categories: Billing rule- (Depends on Business requirement of percentage Basis or Value base etc.)
4. Assign Date category for Billing Plan.
5. Maintain Date proposals for billing plan type: Maintaining the Billing Date, Billing Rule, Date Description and Billing Type Information will be repeated automatically in upcoming milestone orders created in the system (As per client requirement).

6. Assign Billing plan Types to Sales Document Types in SPRO/ Transaction Code: VOFA.
7. Assign Billing Plan type to Item Categories.
8. In some Business Cases Milestone comes from PS Module:

• Create Milestone Billing in Project Systems (PS) Module Use Transaction Code: CJ20N (Project Builder)
  
• Define milestone under project activities and specify milestone dates.
  
• Link each milestone to a billing plan date.
  
• Once the Milestone is confirmed by the Project system team, the billing block is removed and billing can be done accordingly.

9. Create Sales order: Go to Billing plan tab in Item level & adjust the billing dates and amounts according to milestone and project progress.
10. Now system is ready to create Invoices based on Milestone.

Note: To Add or Remove Billing Plan Tab in Sales order – Header level Screen > Go to Transaction code VOV8 Select sales document type in Billing Tab > Billing Plan type maintain as Business requirements.

Advantages of Milestone billing to clients:

Milestone billing gives clients the option to change project focuses while reducing the financial risk by connecting payments to finished milestones. It helps businesses keep high quality, Standard and builds a trust in client. Linking payments to the project phase clears the result encourages trust and openness, Clients can monitor the progress and make sure payments match the billing value delivered. This approach also improves project management by setting clear targets and timelines, which helps stay on schedule and budget while matching cash flow Alignment with project advancement.

Upgrade in S/4HANA compared to ECC:

1. User Interface: Fiori application provides modern & easy to use interface, easy to track and manage.
2. Milestone Achievement rates are progressed due to embedded analytical dashboards and by allowing real- time Tracking.
3. Integration with SAP Project Systems (PS) updates billing milestones by project status, making it more accurate and cutting down on manual tasks.
4. The integration of real-time connectivity with the Universal Journal facilitates instantaneous modifications to milestone billing financial documentation, thereby obviating the necessity for routine verifications.
5. The system provides quicker processing of big billing data and allows for real-time checks for billing results.

Conclusion: Milestone billing is a useful way to send invoices that brings several advantages to companies. These advantages include better cash flow control, improved project handling, and stronger relationships with clients. By linking payments to certain project milestones, companies can maintain financial steadiness, lower financial risk, and encourage quality work. Using milestone billing helps companies succeed and gain both profit and customer satisfaction.

The post Milestone Billing in SAP S/4HANA appeared first on ERP Q&A.

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.

Objective:

1. We will explore how to identify an intercompany sales order.
2. how the system allows for the creation of two invoices?
3. The routines and requirements associated with the pricing procedure and copy control.
4. What is ‘Transaction specific Pricing procedure’ checkbox.
5. Why two different pricing procedures are used
6. How the system understands the quantities to be billed for partially delivered orders.
7. Finally, how to set up the process in S4 Hana.

The intercompany sales process in SAP SD (Sales and Distribution) involves the selling of goods or services from one company code to another company. This process typically occurs when one company within a group of companies sells goods or services to another company within the same group.

In the below scenario One company code (US50) produces goods, and another company code (CA10) distributes those goods to customers. There is no manufacturing plant for CA10.

In this scenario, Sales Organization CA10 will receive an order from Customer 9000002009 for Material 730. However, since Plant CA10 does not have the stock available for this particular material, Sales Organization CA10 will fulfill the order by delivering the material from Plant US50.

Step 1 : BP/Customer – 9000002009 created.

Step 2: Assign Plant- US50 to Sales org – CA10. So Sales Org- CA10 can place order to US50 plant.

Step 3: Material extended to both the plants.

Step 4: Define Order Types For Intercompany Billing

Path : SPRO –> Sales and Distribution –> Billing –> Intercompany Billing –> Define Order Types For Intercompany Billing

Assign sales document type with Intercompany billing type IV. Here we can restrict relevant document types to create Inter company invoice.

Step 5: Assign Organizational Units By Plant

Path : SPRO –> Sales and Distribution –> Billing –> Intercompany Billing –> Assign Organizational Units By Plant

The delivering plant utilizes these configuration to generate the intercompany invoice, using the internal customer number of the ordering sales organization.

Step 6: Define Internal Customer Number By Sales Organization

i ) Internal customer/BP – 9000002011 created for Supplying Sales area.

ii) Path : SPRO –> Sales and Distribution –> Billing –> Intercompany Billing –> Define Internal Customer Number By Sales Organization

The delivering plant using this configurations to process intercompany billing for this customer number.

Step 7: Lets try to create a sales order with plant – US50, before setup all pricing components to validate all org structures.

Getting error to maintain the plant. To resolve this issue follow the below path.

SPRO –> Materials Management –> Purchasing –> Set up Stock Transport Order –> Define Shipping Data for Plants

Now order can be created with Plant – US50.

Step-8: Determination of Pricing Procedure:

Procedure has been setup for CA10 and US50.

Here, a new Customer Pricing procedure (I) has been created for Intercompany Pricing Scenario.

i) Path to create new customer pricing procedure:

Logistics – General –> Settlement Management –> Basic Settings –> Pricing –> Define Customer Pricing Procedures.

ii) Maintain Customer pricing procedure(I) for Internal customer, so that system should determine pricing procedure ZIC01 in case of Intercompany scenario.

Step 9: Configure Pricing

Requirement: The price of US50 is 39,000/- per unit when sold to CA10, and CA10 sells it to customers at a price of 50,000/- per unit.

Lets see how can we achieve this requirement.

Condition value maintain for PR00, PI01 and IV01.

Setup IV01 condition type for intercompany billing which is a reference condition of PI01.

Setup condition- PI01 in procedure ZCA10 as a statistical condition ( cost of CA10) with requirement-22, so it can only be active once company code of plant and sales order will be different.

Maintain condition IV01 (which is a reference condition of PI01) within procedure ZIC01 with requirement 22 and its not a statistical condition as it will be the sales price for US50.

Check “Transaction specific Pricing procedure” checkbox for intercompany pricing procedure.

“Transaction specific Pricing procedure” checkbox :

Before the release of version 4.0, there was no specific pricing procedure in place for Intercompany Billing. Instead, we used the standard pricing procedure (RVAA01) for both customer billing and Intercompany Billing documents. To address this situation, a fixed program was implemented.

However, with the release of version 4.0, a new feature called “Transaction specific Pricing procedure” was introduced, providing greater flexibility for Intercompany Billing. SAP recommends using the standard procedure ICAA01 (document pricing procedure I) for Intercompany Billing documents. Although the previous fixed program was not completely removed for compatibility purposes, we still have the option to utilize the old program logic. This means that if we opt to use a separate pricing procedure for Intercompany Billing documents, we must use the “specific procedure.”

By using a different pricing procedure, we have the flexibility to exclude certain conditions, such as discounts and rebates, that may not be relevant for Intercompany Billing calculations.

Step 10: Create IC Scenario

Now lets create once order to invoice.

Order-5 has been created successfully with the details and pricing is showing correctly.

Here, PI01 correctly determines as a statistical condition which represents the cost price of CA10.

Create delivery and PGI.

Now create standard invoice for delivery.

Now create invoice again against same delivery number.
Intercompany Invoice has been created.

As we see, Intercompany invoice has been created for internal customer for company code- US50 and pricing procedure- ZIC01.

IV01 derives the amount from PI01 due to reference condition settings.

PI01 (cost from standard pricing procedure) become Sales price of intercompany invoice.

System allows to creates 2 invoices from single delivery due to below copy control setting. Requirement -014 also checks how may quantities actually delivered to customer from sales order.

The post Intercompany Sales Process in S4 Hana: Comprehensive Guide to Configurations and Their Significance appeared first on ERP Q&A.

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

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

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

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

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.

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

• 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

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

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:

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

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

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:

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

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

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

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:

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

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:

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

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 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

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.

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.

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:

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.

A Brazilian Company named “Samba com Feijoada Inc.” manufactures cavaquinhos, tamborins and some others Samba Instruments

This company, due to Covid-19, needs to avoid human contact unless it’s really necessary. So, when a truck arrives at the company’s parking lot, the Logistics Teams needs to know what is the freight order(SAP TM) in order to start the dispatch process.

Earlier, when truck arrives a person would do the first contact with the driver and take the truck data, that is not a option now.

Solution Design

In this scenario, Samba e Feijoada needs a ChatBot, and the tool to connect with this ChatBot will be Telegram (Popular messaging app, light, fit the need to work in almost every smartphone)

Truck Driver arrives, he/she access Telegram on his/her phone, find our Bot and text “check freight order number”.

Our solution needs to verify if the Freight Order is in the correct Status, if it is, it needs to verify the deliveries status are ok, if they are, give the possibility to the driver generate a billing document request for the whole freight order (it’ll make the waiting in the truck faster) or just wait.

In Brazil, we have a legal requirement to generate the billing prior to the truck leave the plant with the goods

In every case, the solution needs to inform the Logistics Team the truck arrived and the status of the freight order/Deliveries. This communication will be done through e-mail.

Solution Screenshots

This is FejucaBot

First interaction and responses(small talk)

Truck Arrival Solution Part 1

Truck Arrival “Help them”

Websites “Wait”

E-mail example (Sent to Logistics Team)

How did we build FejucaBot

First Steps

Enter SAP CAI Website and create your account or Sign On

Click on New Bot

Choose the type of Bot, FejucaBot is a Perform Actions type

Choose standard skills, FejucaBot knows Greetings, Small Talk and Weather (a real gentleman)

Give a name to your Bot, and choose the main language (you can add more languages later, so don’t worry)

Choose Data Policy

Choose Bot Visibility (In this case we chose private because there is a access to a SAP S/4 Hana application, and unfortunately we cannot share it)

Then, click on Create a Bot

Intent

We will need three intents for FejucaBot. A initial one to get the Freight Order using phrases like “Check Freight Order 99999999999” or “Check 99999999999”, one for Waiting and another for Generate Billing Requests

So click on +Create (Train – Intent)

Insert the phrases that will trigger your skill

Skills

Click on Build and then on Add Skill

Click on Skill Name and then in trigger, assign your intent to the skill. This means everytime someone text FejucaBot “check 9999999”, SAP CAI will trigger skill Check Freight Order

Then, click on Requirements, insert the fields (Available on Intent) your skill needs, at this moment you can assign an alias.

Now, click on Actions

Fejuca Bot was build using Connect External Service(API), Edit Memory and Send Message.

Connect External Service API 1

In a single GET in CPI, we connect on a S/4 Hana 1909 Application.

First, we build a Custom CDS View for the SAP Transportation Management tables, in this API we get the Status of the document and the deliveries.

Second, in a standard API for Outbound Deliveries, we verify if these deliveries are ready to be invoiced (if needed)

Then CPI send an email to the Logistics Team informing the truck arrival, freight order and status.

Finally it sends back to SAP CAI the status and the Freight Order data.

Send Message 1

Using system variables as $freightorder $status and $address, we send a custom message for each status of Freight Order, If the freight Order does not exists, a message is sent as well.

Connect External Service API 2

After the first CPI interaction, if the status is 100% ok, we have the final destination partner for this Freight Order, then we do another Standard API for Business Partner to get the address of the final destination partner.

Send Message 2

Verify that this message will trigger two skills:

Help Them

It will trigger a POST API on CPI(Creating the Invoice Requests) and send an email to the team.

Wait

It will trigger a simple skill as below and send an email.

It will also trigger a POST API on CPI(with a different header parameter) and send an email to the team.

Telegram

To connect to Telegram, click on Connect and then on Telegram, SAP CAI already have a good tutorial about it.

Improvement Ideas

The solution works, but it is not perfect, the good people from IT of Samba com Feijoada Inc already assemble a RoadMap

• Verify the location of the truckdriver through GPS, to be sure he is close to the plant
  
• Verify the IP Address, and provide a Wi-fi connection in the parking lot.
  
• Catch the License Plate, name and ID of the driver, and later updates in the Freight Order

The post Challenge Submission – Introducing FejucaBot appeared first on ERP Q&A.