SAP Community - SAP ERP

REM Manufacturing

2024-03-26T20:23:57.879000+01:00

Repetitive manufacturing (REM) needs below mentioned mandatory master data for
Repetitive manufacturing process.
1. Material Master data
2. Production Version
3. BOM
4. Rate routing.
5. REM Profile
6. Product Cost collector

Production version is combination of BOM and Rate routing. This maintained in
MRP4 view of material master.
REM Profile need to configure if need and maintain that in MRP4 of Material master.
Finish Material and sub-assemblies should have BOM (Bill of material) and Rate Routing.

Product cost collector is cost Object in REM manufacturing Process. Planned order is final receipt which will not convert to production order. All activity cost, material consumption cost will settle in product cost collector.

Finish material should have demand either customer or planned independent requirement (PIR). Based on those demand, MRP will generate Planned order with order type “PE” are also called as Run schedule.

If sub-assemblies are with Procurement type E, REM Profile and Production version, then MRP generate Run schedule for those also.

That run schedule creates dependent requirements for all BOM components which are production relevant.

Planning could run at Plant level through MD01 transaction. Planning could also run at material level through MD02.

Before Manufacturing confirmation, Cost of materials should estimate and released.

Cost of Product cost collector should also estimate.

Manufacturing execution:

Quantity and activity could confirm based on business process.

When quantity of Finish material/Sub-assemblies confirmed, this reduces planned order quantity of those materials and that of dependent material also.

During manufacturing confirmation, BOM could explode, and components could consume automatically based on setting in REM profile.

If materials are linked with Non-HU (Handling unit) storage location, then those could be confirmed through transaction MFBF.

If Finish Materials are linked with HU (Handling Unit) storage location, then production confirmation could happen with reference to Handling Unit in transaction MFHU.

Quantity linked to Handling unit will confirm.

After manufacturing confirmation, Planned order qty reduced from 5 to 1.

Updates on Conhecimento de Transporte Eletrônico and Manifesto Eletrônico de Documentos Fiscais

2024-03-27T20:15:42.857000+01:00

Hi everyone,

The SAP Document and Reporting Compliance, inbound and outbound invoicing options for Brazil team has released updates on Conhecimento de Transporte Eletrônico (CT-e) and Manifesto Eletrônico de Documentos Fiscais (MDF-e). The update complies with SEFAZ CT-e Technical Note 2024.001 1.01 Version (Tax Benefit Inclusion) and MDF-e Technical Note 2024.001 1.01 Version (Closing Event). The new version is planned to be in production on April 8, 2024, according to the tax authority.

Updates on CT-e and MDF-e Technical Note 2024.001 - Version 1.01

Conhecimento de Transporte Eletrônico (CT-e):

The new update on CT-e (model 57) and CT-e OS (model 67) allows you to include the new vICMSDeson (Exempt ICMS Tax) and cBenef (Fiscal Benefit Code) fields in the XML files. These fields will be included in the following ICMS groups: ICMS20, ICMS45, ICMS60, ICMS90, and ICMSOutraUF.

You can implement these updates by following the instructions on the SAP Notes:

SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824
SAP Note 3441171
SAP Note 3445374

You can implement the changes for the SAP Electronic Invoicing for Brazil (SAP NFE) solution following the instructions on SAP Notes:

SAP Note 3426934
SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824

The SEFAZ CT-e Technical Note 2024.001 1.02 Version has been revised, and there will be no impact on the CT-e solution.

Check SAP Knowledge Base Article 2807654 for troubleshooting information and common issues.

Manifesto Eletrônico de Documentos Fiscais (MDF-e):

The update on MDF-e (model 58) allows you to include the indEncPorTerceiro field in the XML files, which has been introduced to the closing event (type 110112). To implement this update, follow the instructions on SAP Note 3437854.

The SEFAZ MDF-e Technical Note 2024.001 1.02 Version has been revised. The XML schema has been updated in our service, and it is not necessary to implement other SAP Notes for this change.

You can implement the changes for the SAP Electronic Invoicing for Brazil (SAP NFE) solution by following the instructions on SAP Note 3431096.

Related blog posts:

For a step-by-step guide on how to use the SAP Document and Reporting Compliance, inbound and outbound invoicing options for Brazil, refer to the following SAP Help Portal pages:

You can sign up for email alerts when new SAP Notes are released or updated in the components listed below; just follow the instructions in the SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE
SLL-NFE

Use the regulatory change manager tool to find out if a solution to a legal change is planned. Take a look at SAP Knowledge Base Article 3421995 and the regulatory change manager page to understand how to use this tool.

Have you found this blog post useful? If so, choose “Like” (Kudos), share it with your colleagues, and follow me for similar content.

You are welcome to leave your questions and read similar blog posts on the SAP Document and Reporting Compliance SAP Community. Don’t forget to follow the SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) tag and the SAP Document and Reporting Compliance Community to keep up with the latest NF-e news.

Thank you, and until next time,
Thiago

Tags: electronic transportation document, nota técnica, v1.01, 2024/001, inclusão do benefício fiscal, tax benefit inclusion, tax benefit code, código de benefício fiscal, documento fiscal eletrônico, electronic fiscal document, electronic manifest of tax documents, brasil, einvoice, einvoicing, e-invoicing, electronic invoice, electronic invoicing, edocument, edoc, e-document, e-docs, e-doc, e-docs, drc, document compliance, nota fiscal eletrônica, electronic nota fiscal, ct-e outros serviços, ct-e other services.

NF-e Technical Note 2019.001 v1.62: New Fields Added to Nota Fiscal

2024-03-28T21:27:28.599000+01:00

Hello, everybody

The Brazilian government has published technical note 2019.001 v1.62-SEFAZ, which provides for the inclusion of fields for presumed credit information and the addition of a fiscal benefit code for base reduction within CST 51 (Tax Situation Code 51), when there is accumulation with deferment, as well as the creation and updating of validation rules. Click here for the Portuguese version.

In this blog post, we will cover the following topics available for SAP S/4HANA and SAP ERP:

Updates related to the new and changed fields.
Relevant SAP Notes for this legal requirement.

New fields added to the system

New table and fields for presumed credit information

To meet this legal requirement, the new fields State Fiscal Benefit Code of Presumed Credit (C_CRED_PRESUMIDO), Presumed Credit Percentage (P_CRED_PRESUMIDO), and Presumed Credit Amount (V_CRED_PRESUMIDO) have been added to the new table Nota Fiscal Presumed Credit (J_1BNFPRSMD_CRDT).

The fields refer to the presumed credit benefit code defined by the UF of the nota fiscal issuer, the percentage of the presumed credit, and the presumed credit value related to the presumed credit tax benefit.

New field for fiscal benefit code

The field State Fiscal Benefit Code ICMS Deferral with Base Reduction (CBENEF_RBC) has been added to the existing structure Nota Fiscal Additional Item Fields (J_1BNFLIN_ADD). This field specifies the code related to fiscal benefits (cBenefRBC) in case tax base reduction (RBC) accumulates with ICMS deferral (CST51), applied to each state according to the item inserted in your Electronic Nota Fiscal (NF-e).

The changes mentioned in this blog post are available in the following system objects for SAP ERP, SAP S/4HANA:

Nota Fiscal Writer Transactions (J1B*N)
- Nota Fiscal Presumed Credit (J_1BNFPRSMD_CRDT), under the Taxes tab.
- Nota Fiscal line items (J_1BNFLIN), under the Items tab
Nota Fiscal System – Create Object from data (BAPI_J_1B_NF_CREATEFROMDATA) BAPI
Nota Fiscal: List details of a Nota Fiscal (BAPI_J_1B_NF_READDATA) BAPI
Additional Data for Nota Fiscal (J_1BNF_ADD_DATA) BAdI

In both BAPIs, the parameter for Nota Fiscal Presumed Credit is OBJ_PRESUMED_CREDIT. In the BAdI the parameter is ET_PRSMD_CRDT.

Relevant SAP Notes for this legal requirement

You can install the following SAP Notes to update your solution:

SAP Note 3423951 – NF-e Technical Note 2019.001 v1.61: Prerequisite objects for SAP Note 3423952
SAP Note 3423952 – NF-e Technical Note 2019.001 v1.61: New Fields Added to Nota Fiscal for Presumed Credit and Fiscal Benefit Code

You can implement these updates in the SAP Document and Reporting Compliance, outbound invoicing option for Brazil (LOD-LH-NFE component) and Nota Fiscal Eletrônica Outbound (FI-LOC-NFE-BR-OUT component) by following the instructions on the SAP Notes:

SAP Note 3440649 – Outbound NF-e: Prerequisite Objects of SAP Note 3447619
SAP Note 3447619 – Outbound NF-e: NF-e Technical Note 2019.001 v1.62 and 2023.004 v1.11

These SAP Notes deliver the new gCred group and the new cBenefRBC field on the ICMS51 group in the layout of the XML file. Additionally, the product information will now include three new fields (cCredPresumido, pCredPresumido, and vCredPresumido) for presumed credit.

You can also implement the changes for the SAP Electronic Invoicing for Brazil (SAP NFE) solution by following the instructions on SAP Note 3426933 – NF-e NT2019.001 & NT2023.004.

Use the regulatory change manager tool to find out if a solution is planned for a legal change. For the NF-e Technical Note 2019.001 v1.61, check the URL NF-e Technical Note 2019.001 v1.61. Take a look at the SAP Knowledge Base Article 3421995 and the Regulatory Change Manager page to understand how to use this tool.

For more information, check the SAP Knowledge Base Article 2955945 - NF-e Technical Note 2019.001 v1.61 Troubleshooting Guide

Update - 05 April, 2024

Follow the steps on the SAP Notes below to implement the updates in the SAP Document and Reporting Compliance, inbound invoicing option for Brazil:

SAP Note 3444168 – Incoming NF-e: Technical Note 2019.001 v1.62 and 2023.004 v1.11
SAP Note 3441355 – eDocument Brazil Inbound NF-e: Prerequisite Objects for SAP Note 3447713
SAP Note 3447713 – eDocument Brazil Inbound NF-e: Technical Note 2019.001 v1.62 and 2023.004 v1.11

Did you like this post? Give it a Like (kudo) and share the content with your colleagues. Feel free to leave feedback, comment, or question in the space below. And don’t forget to follow the SAP S/4HANA Logistics for Brazil tag in the SAP Community to stay tuned for the latest news.

Regards,

Luize Boyen

NF-e Nota Técnica 2019.001 v1.62 novos campos adicionados à nota fiscal

2024-03-28T21:27:41.367000+01:00

Olá, pessoal

O governo brasileiro publicou a nota técnica 2019.001 v1.62-SEFAZ, que disponibiliza a inclusão de campos para as informações de crédito presumido e a adição do código de benefício fiscal para a redução da base de cálculo quando acumulada ao diferimento (CST 51 - Código de Situação Tributária 51), e criação e atualização de regras de validação. Clique aqui para a versão em inglês.

Nesse blog post, abordaremos os seguintes tópicos disponíveis para SAP ERP e SAP S/4HANA:

Atualizações referentes aos novos campos adicionados.
SAP Notes relevantes para esse requisito legal.

Novos campos adicionados ao sistema

Nova tabela e campos para informações de crédito presumido

Para atender esse requisito legal, os novos campos State Fiscal Benefit Code of Presumed Credit (C_CRED_PRESUMIDO), Presumed Credit Percentage (P_CRED_PRESUMIDO) e Presumed Credit Amount (V_CRED_PRESUMIDO) foram adicionados a nova tabela Nota Fiscal Presumed Credit (J_1BNFPRSMD_CRDT).

Os campos se referem ao código de benefício fiscal de crédito presumido definido pela UF do emissor da nota fiscal, o percentual do crédito presumido, e o valor do crédito presumido relativos ao benefício fiscal de crédito presumido.

Novo campo para código de benefício fiscal

Já o campo State Fiscal Benefit Code ICMS Deferral with Base Reduction (CBENEF_RBC) foi adicionado a estrutura existente Nota Fiscal Additional Item Fields (J_1BNFLIN_ADD) e refere-se ao código de benefício fiscal utilizado pela UF do emissor da nota fiscal no caso de acumulação de redução de base de cálculo (RBC) com diferimento de ICMS (CST51), aplicado a cada estado de acordo com o item inserido na sua Nota Fiscal Eletrônica (NF-e).

As alterações mencionadas neste blog post estão disponíveis nos seguintes objetos do sistema para SAP ERP, SAP S/4HANA:

Transações da Nota Fiscal Writer (J1B*N)
- Nota Fiscal Presumed Credit (J_1BNFPRSMD_CRDT),na aba Taxes
- Nota Fiscal line items (J_1BNFLIN), na aba Items
Nota Fiscal System – Create Object from data (BAPI_J_1B_NF_CREATEFROMDATA) BAPI
Nota Fiscal: List details of a Nota Fiscal (BAPI_J_1B_NF_READDATA) BAPI
Additional Data for Nota Fiscal (J_1BNF_ADD_DATA) BAdI

Em ambas as BAPIs, o parâmetro para Nota Fiscal Presumed Credit é OBJ_PRESUMED_CREDIT. Na BAdI o parâmetro da nova tabela é ET_PRSMD_CRDT.

SAP Notes relevantes para esse requisito legal

Você pode instalar as seguintes SAP Notes para atualizar a sua solução:

SAP Note 3423951 – NF-e Technical Note 2019.001 v1.62: Prerequisite objects for SAP Note 3423952
SAP Note 3423952 – NF-e Technical Note 2019.001 v1.62: New Fields Added to Nota Fiscal for Presumed Credit and Fiscal Benefit Code

Você pode implementar essas atualizações no SAP Document and Reporting Compliance, opção de faturamento de saída para o Brasil (componente LOD-LH-NFE) e Nota Fiscal Eletrônica Outbound (componente FI-LOC-NFE-BR-OUT) seguindo as instruções nas SAP Notes:

SAP Note 3440649 – Outbound NF-e: Prerequisite Objects of SAP Note 3447619
SAP Note 3447619 – Outbound NF-e: NF-e Technical Note 2019.001 v1.62 and 2023.004 v1.11

No layout do arquivo XML, essas SAP Notes entregam o novo grupo gCred e o novo campo cBenefRBC no grupo ICMS51. As informações de produto contêm agora três novos campos (cCredPresumido, pCredPresumido and vCredPresumido) para crédito presumido.

Você também pode implementar as alterações na solução SAP Electronic Invoicing for Brazil (SAP NFE) seguindo as instruções da SAP Note 3426933 – NF-e NT2019.001 & NT2023.004.

Use a ferramenta regulatory change manager para descobrir se uma solução está planejada. Para a Nota técnica da NF-e 2019.001 v1.62, consulte a URL NF-e Technical Note 2019.001 v1.62. Para entender como usar essa ferramenta, consulte o SAP Knowledge Base Article 3421995 e a página do Regulatory Change Manager.

Para mais informações, consulte o SAP Knowledge Base Article 2955945 - NF-e Technical Note 2019.001 v1.62 Troubleshooting Guide

Atualização - 05 de abril de 2024

Para implementar as atualizações no SAP Document and Reporting Compliance, opção de emissão de fatura de entrada para o Brasil, siga as etapas nas SAP Notes abaixo:

SAP Note 3444168 – Incoming NF-e: Technical Note 2019.001 v1.62 and 2023.004 v1.11
SAP Note 3441355 – eDocument Brazil Inbound NF-e: Prerequisite Objects for SAP Note 3447713
SAP Note 3447713 – eDocument Brazil Inbound NF-e: Technical Note 2019.001 v1.62 and 2023.004 v1.11

Gostou desse post? Dê um Like (kudo) e compartilhe o conteúdo com seus colegas. Fiquem à vontade para deixar um feedback, comentário ou pergunta no espaço abaixo. E não esqueça de seguir a tag SAP S/4HANA Logistics for Brazil na SAP Community para ficar ligado nas últimas notícias.

Um abraço,

Luize Boyen

NF-e Nota Técnica 2023.004 v1.10: novos campos adicionados à nota fiscal (Cloud)

2024-04-01T16:06:44.569000+02:00

Olá, pessoal

O governo brasileiro publicou a nota técnica 2023.004 v1.10-SEFAZ, que disponibiliza a inclusão de campos e alteração de campos existentes e regras de validação para os grupos Documentos de Importação, ICMS e Informação de Pagamento para nota fiscal eletrônica (NF-e). Clique aqui para versão em inglês.

Nesse blog post, abordaremos sobre atualizações referentes aos campos adicionados e alterados disponíveis para SAP S/4HANA Cloud:

Novos campos adicionados ao sistema

Grupo de Documentos de Importação

Foi adicionado o novo campo CPF Number à tabela Nota Fiscal Data for Import Documents.

Grupo de ICMS

O novo campo Exempted ICMS value deduction from the nota fiscal total foi adicionado à tabela existente Nota Fiscal line items. Esse indica se o valor ICMS isento é deduzido.

Grupo de Informações de Pagamento:

Os novos campos Payment Recipient CNPJ, Payment terminal identifier , Payment Date , Payment Transactional CNPJ e Region of the establishment's CNPJ where the payment is made foram adicionados à tabela existente Payment Information.

Mudanças em campos já existentes no sistema

O campo Authorization Number na Payment Information table agora suporta até 128 caracteres.

No grupo, foi adicionada a seguinte entrada no intervalo de valores do campo Process Origin Indicator:

4-CONFAZ

Também foram adicionadas novas entradas ao intervalo de valores do campo Type Of Concession Act:

14-SINIEF Adjustment
15-ICMS Agreement

As alterações mencionadas neste blog post estão disponíveis nos seguintes objetos do sistema para SAP S/4HANA Cloud:

Create Nota Fiscal app
Change Nota Fiscal app
Display Nota Fiscal app
Additional Data for Nota Fiscal Cloud BAdI

Gostou desse post? Dê um Like e compartilhe o conteúdo com seus colegas. Fiquem à vontade para deixar um feedback, comentário ou pergunta no espaço abaixo. E não esqueça de seguir a tag SAP S/4HANA Cloud Logistics for Brazil na SAP Community para ficar ligado nas últimas notícias.

Um abraço,

Luize Boyen

How to add a new field to the VL06O,VL06I, VL06G… screens?

2024-04-03T10:55:12.936000+02:00

This article explains step by step what to do when adding a new field to vlo6*(VL06O, VL06I, VL06G, VL06P, VL06T, VL06F, VL06C, VL06IP, VL06IC, VL06IT, VL06IG, VL06IF) screens

you can check https://me.sap.com/notes/128150

Scenario: let's add the definition of delivery type(VTEXT field)

In transaction code CMOD, choose 'Utilities -> SAP Enhancements

Enter the name of the enhancement 'V50Q0001' and execute

Double click on exit name to display function exits

We have to check if the includes are active

If exits are active, when we click on CMOD components they should appear active as follows. If it does'nt appear active in this way, we can assign

Then we go to SE11 to LIPOV which is the structure where we will add the field

Give database table and in change mode.

Click append structure and give new name.

Double click the component type and add related fields to structure VTEXT

Check that the relevant field is active and saved in the append structure as follows

The field we added comes to VL06O empty

We write the following code block in exit for the definitions to come in

Delivery type definitions come like this

I would be happy to read your thoughts and comments and if there are better ways to fulfil the requirement, please leave them in the comment section below.

Thanks so much

Linear programming in ABAP. Simplex method. Find optimised BOM

2024-04-07T00:58:49.597000+02:00

This is a short post regarding linear programming (LP) and Simplex method in ABAP. I’ve tried to find some standard SAP functionality, but with no success (except a small demo program GENIOS_TEST_DEMO). Maybe I’m reinventing a wheel here, so, if somebody knows it – please let me know (maybe it could be part of PP, APO or IBP functionality).

Below you may find a simple basic description how some of LP problem can be solve via standard SAP class cl_genios_environment.

What is LP?

Linear programming (LP), also called linear optimization, is a method to achieve the best outcome (such as maximum profit or lowest cost) in a mathematical model whose requirements and objective are represented by linear relationships. Linear programming is a special case of mathematical programming (also known as mathematical optimization).

Link to the WIKI https://en.wikipedia.org/wiki/Linear_programming

Example of optimization task. Creating an optimal BOM with necessary characteristics

As one of the optimisation task which can be solved by LP let’s take this one:

We need to create a some blend from raw materials with characteristics as shown below, with components percentage:

N >=15%,
P >=15%,
K >=70%.

*N/P/K is a components of a material. These components also contain in a raw materials, but in a different components percentages.

Raw material	N, %	P, %	K, %	Price per KG
Material 1 (x1)	12	12	76	35 EUR
Material 2 (x2)	20	18	62	52 EUR
Material 3 (x3)	12	18	70	40 EUR
Material 4 (x4)	20	14	66	46 EUR

As an assumption – component percentage are mass based.

Requirements: find optimal (with less total price) bill of material (BOM) to create 1KG of this blend.

Let's create an economic-mathematical model of the problem:

Define as:
x1 – quantity of Material 1 in target blend, in kg
x2 – …Material 2, kg
x3 – …Material 3, kg
x4 – …Material 4, kg

Restriction of components percentages can be formalized as system of linear inequations :
12*<x1> + 20*<x2> + 12*<x3> + 20*<x4> ≥ 15*(<x1> + <x2> + <x3> + <x4>)
12*<x1> + 18*<x2> + 18*<x3> + 14*<x4> ≥ 15*(<x1> + <x2> + <x3> + <x4>)
76*<x1> + 62*<x2> + 70*<x3> + 66*<x4> = 70*(<x1> + <x2> + <x3> + <x4>)

Left side: percentage of N/P/K in raw materials multiply by quantity of raw materials in final blend

Right side: Target blend N/P/K characteristics

Restriction of total blend quantity should be equal to 1kg, let’s put it as an additional at the previous inequations
<x1> + <x2> + <x3> + <x4> = 1 (kg)

Final blend price function, which should be optimized is:
35*<x1> + 52*<x2> + 40*<x3> + 46*<x4> → min

This is a sum of price multiply by quantity of each raw material in target blend.

How it can be solved in math way

Let's solve the linear programming problem using the dual simplex method and simplex tables.

https://en.wikipedia.org/wiki/Simplex_algorithm

Reduce the system of inequalities to a system of equations by introducing additional variables (x5 ,x6 ,x7):

12*x1+20*x2+12*x3+20*x4+x5 = 15
12*x1+18*x2+18*x3+14*x4+x6 = 15
76*x1+62*x2+70*x3+66*x4+x7 = 70
x1+x2+x3+x4 = 1

Extended matrix of the system of equalities constraints will be:

12	20	12	20	1	0	0	15
12	18	18	14	0	1	0	15
76	62	70	66	0	0	1	70
1	1	1	1	0	0	0	1

And we can find an optimal values via simplex method.

Spoiler

Let's reduce matrix to the JCF https://en.wikipedia.org/wiki/Jordan_normal_form .

Base variable will be x4.

The line corresponding to the variable x4 is obtained by dividing all elements of the line x4 by the 1. In the remaining cells of the x4 column we write zeros.

Let's show the calculation of each element in the table below:

12-(1*20) /1	20-(1*20) /1	12-(1*20) /1	20-(1*20) /1	1-(0*20) /1	0-(0*20) /1	0-(0*20) /1	15-(1*20) /1
12-(1*14) /1	18-(1*14) /1	18-(1*14) /1	14-(1*14) /1	0-(0*14) /1	1-(0*14) /1	0-(0*14) /1	15-(1*14) /1
76-(1*66) /1	62-(1*66) /1	70-(1*66) /1	66-(1*66) /1	0-(0*66) /1	0-(0*66) /1	1-(0*66) /1	70-(1*66) /1
1 / 1	1 / 1	1 / 1	1 / 1	0 / 1	0 / 1	0 / 1	1 / 1

New JCF matrix will be like:

-8	0	-8	0	1	0	0	-5
-2	4	4	0	0	1	0	1
10	-4	4	0	0	0	1	4
1	1	1	1	0	0	0	1

Let’s take as a basic variables x5, x6, x7 and x4 and calculate the basic variables in terms of the other variables:

x5 = 8*x1+8*x3-5
x6 = 2*x1-4*x2-4*x3+1
x7 = -10*x1+4*x2-4*x3+4
x4 = -x1-x2-x3+1

Now put them into the target function:

F(X) = 35*x1+52*x2+40*x3+46*(-x1-x2-x3+1) or F(X) = -11*x1+6*x2-6*x3+46
-8*x1-8*x3+x5=-5
-2*x1+4*x2+4*x3+x6=1
10*x1-4*x2+4*x3+x7=4
x1+x2+x3+x4=1

And create a new matrix:

-8	0	-8	0	1	0	0
-2	4	4	0	0	1	0
10	-4	4	0	0	0	1
1	1	1	1	0	0	0

Basic variables are variables that are included in only one equation of the system of constraints and, moreover, with a 1 coefficient.

Economic meaning of additional variables: additional variables of the LP problem indicate the surplus of raw materials, time, and other resources remaining in the production of a given optimal plan.

Let's solve the system of equations for the basic variables: x5, x6, x7, x4

Assuming that the free variables(x1,x2,x3) are equal to 0, we obtain the first possible solution (#0):
X0 = (0,0,0,1,-5,1,4)
The basic solution is acceptable if it is non-negative.

Basis	B	x1	x2	x3	x4	x5	x6	x7
x5	-5	-8	0	-8	0	1	0	0
x6	1	-2	4	4	0	0	1	0
x7	4	10	-4	4	0	0	0	1
x4	1	1	1	1	1	0	0	0
F(X0)	0	11	-6	6	0	0	0	0

Checking the optimality criterion - Not optimal.

This possible solution (#0) in a simplex table is a pseudo-solution, so we need to determine the leading row and column.
Definition of a new free variable.

Among the negative values of the basic variables, we select the largest in absolute value.

The leading line will be the 1st line, and the variable x5 should be derived from the basis.
Definition of a new basic variable.

The minimum value of θ corresponds to the 3rd column, i.e. the variable x3 must be entered into the basis.

At the intersection of the leading row and column there is a value equal to -8.

Basis	B	x1	x2	x3	x4	x5	x6	x7
x5	-5	-8	0	-8	0	1	0	0
x6	1	-2	4	4	0	0	1	0
x7	4	10	-4	4	0	0	0	1
x4	1	1	1	1	1	0	0	0
F(X0)	0	11	-6	6	0	0	0	0
θ		-11/8	-	6/-8 = -3/4	-	-	-	-

Recalculation of the simplex table.

Carry out transformations of the simplex table using the Gauss-Jordan method
Let's one more time show the calculation of each element in a table:

B	x1	x2	x3	x4	x5	x6	x7
-5 / -8	-8 / -8	0 / -8	-8 / -8	0 / -8	1 / -8	0 / -8	0 / -8
1-(-5*4) /-8	-2-(-8*4) /-8	4-(0*4) /-8	4-(-8*4) /-8	0-(0*4) /-8	0-(1*4) /-8	1-(0*4) /-8	0-(0*4) /-8
4-(-5*4) /-8	10-(-8*4) /-8	-4-(0*4) /-8	4-(-8*4) /-8	0-(0*4) /-8	0-(1*4) /-8	0-(0*4) /-8	1-(0*4) /-8
1-(-5*1) /-8	1-(-8*1) /-8	1-(0*1) /-8	1-(-8*1) /-8	1-(0*1) /-8	0-(1*1) /-8	0-(0*1) /-8	0-(0*1) /-8
0-(-5*6) /-8	11-(-8*6) /-8	-6-(0*6) /-8	6-(-8*6) /-8	0-(0*6) /-8	0-(1*6) /-8	0-(0*6) /-8	0-(0*6) /-8

Result:

Basis	B	x1	x2	x3	x4	x5	x6	x7
x3	5/8	1	0	1	0	-1/8	0	0
x6	-3/2	-6	4	0	0	1/2	1	0
x7	3/2	6	-4	0	0	1/2	0	1
x4	3/8	0	1	0	1	1/8	0	0
F(X0)	-15/4	5	-6	0	0	3/4	0	0

One more time make a calculation with 2nd row and x6 and 1st column and put x1 as a basis variable.

Basis	B	x1	x2	x3	x4	x5	x6	x7
x3	5/8	1	0	1	0	-1/8	0	0
x6	-3/2	-6	4	0	0	1/2	1	0
x7	3/2	6	-4	0	0	1/2	0	1
x4	3/8	0	1	0	1	1/8	0	0
F(X0)	-15/4	5	-6	0	0	3/4	0	0
θ		-5/6	-	-	-	-	-	-

Carry out transformations of the simplex table using the Gauss-Jordan method one more time:

Basis	B	x1	x2	x3	x4	x5	x6	x7
x3	3/8	0	2/3	1	0	-1/24	1/6	0
x1	1/4	1	-2/3	0	0	-1/12	-1/6	0
x7	0	0	0	0	0	1	1	1
x4	3/8	0	1	0	1	1/8	0	0
F(X1)	-5	0	-8/3	0	0	7/6	5/6	0

Here’s all elements at basis columns > 0.

Checking the optimality criterion - not optimal because there are positive coefficients in the index row.
Definition of a new basic variable - x5 as the largest coefficient.
Definition of a new free variable. min (- , - , 0 : 1 , 3/8 : 1/8 ) = 0. Therefore, the 3rd line is the leading one.

Basis	B	x1	x2	x3	x4	x5	x6	x7	min
x3	3/8	0	2/3	1	0	-1/24	1/6	0	-
x1	1/4	1	-2/3	0	0	-1/12	-1/6	0	-
x7	0	0	0	0	0	1	1	1	0
x4	3/8	0	1	0	1	1/8	0	0	3
F(X1)	-5	0	-8/3	0	0	7/6	5/6	0	0

And one more time. Final simplex table will be like this:

Basis	B	x1	x2	x3	x4	x5	x6	x7
x3	3/8	0	2/3	1	0	0	5/24	1/24
x1	1/4	1	-2/3	0	0	0	-1/12	1/12
x5	0	0	0	0	0	1	1	1
x4	3/8	0	1	0	1	0	-1/8	-1/8
F(X)	-5	0	-8/3	0	0	0	-1/3	-7/6

Checking the optimality criterion - Optimal!

There are no positive values among the index string values. Therefore, this table determines the optimal solution for the problem.

Let's reduce matrix to the JCF https://en.wikipedia.org/wiki/Jordan_normal_form .Base variable will be x4.The line corresponding to the variable x4 is obtained by dividing all elements of the line x4 by the 1. In the remaining cells of the x4 column we write zeros.Let's show the calculation of each element in the table below:12-(1*20)/120-(1*20)/112-(1*20)/120-(1*20)/11-(0*20)/10-(0*20)/10-(0*20)/115-(1*20)/112-(1*14)/118-(1*14)/118-(1*14)/114-(1*14)/10-(0*14)/11-(0*14)/10-(0*14)/115-(1*14)/176-(1*66)/162-(1*66)/170-(1*66)/166-(1*66)/10-(0*66)/10-(0*66)/11-(0*66)/170-(1*66)/11 / 11 / 11 / 11 / 10 / 10 / 10 / 11 / 1New JCF matrix will be like:-80-80100-5-2440010110-440001411110001 Let’s take as a basic variables x5, x6, x7 and x4 and calculate the basic variables in terms of the other variables:x5 = 8*x1+8*x3-5x6 = 2*x1-4*x2-4*x3+1x7 = -10*x1+4*x2-4*x3+4x4 = -x1-x2-x3+1Now put them into the target function:F(X) = 35*x1+52*x2+40*x3+46*(-x1-x2-x3+1) or F(X) = -11*x1+6*x2-6*x3+46-8*x1-8*x3+x5=-5-2*x1+4*x2+4*x3+x6=110*x1-4*x2+4*x3+x7=4x1+x2+x3+x4=1And create a new matrix:-80-80100-244001010-4400011111000Basic variables are variables that are included in only one equation of the system of constraints and, moreover, with a 1 coefficient.Economic meaning of additional variables: additional variables of the LP problem indicate the surplus of raw materials, time, and other resources remaining in the production of a given optimal plan.Let's solve the system of equations for the basic variables: x5, x6, x7, x4Assuming that the free variables(x1,x2,x3) are equal to 0, we obtain the first possible solution (#0):X0 = (0,0,0,1,-5,1,4)The basic solution is acceptable if it is non-negative.BasisBx1x2x3x4x5x6x7x5-5-80-80100x61-2440010x7410-440001x411111000F(X0)011-660000Checking the optimality criterion - Not optimal.This possible solution (#0) in a simplex table is a pseudo-solution, so we need to determine the leading row and column.Definition of a new free variable.Among the negative values of the basic variables, we select the largest in absolute value.The leading line will be the 1st line, and the variable x5 should be derived from the basis.Definition of a new basic variable.The minimum value of θ corresponds to the 3rd column, i.e. the variable x3 must be entered into the basis.At the intersection of the leading row and column there is a value equal to -8. BasisBx1x2x3x4x5x6x7x5-5-80-80100x61-2440010x7410-440001x411111000F(X0)011-660000θ -11/8- 6/-8 = -3/4- - - - Recalculation of the simplex table.Carry out transformations of the simplex table using the Gauss-Jordan methodLet's one more time show the calculation of each element in a table:Bx1x2x3x4x5x6x7-5 / -8-8 / -80 / -8-8 / -80 / -81 / -80 / -80 / -81-(-5*4)/-8-2-(-8*4)/-84-(0*4)/-84-(-8*4)/-80-(0*4)/-80-(1*4)/-81-(0*4)/-80-(0*4)/-84-(-5*4)/-810-(-8*4)/-8-4-(0*4)/-84-(-8*4)/-80-(0*4)/-80-(1*4)/-80-(0*4)/-81-(0*4)/-81-(-5*1)/-81-(-8*1)/-81-(0*1)/-81-(-8*1)/-81-(0*1)/-80-(1*1)/-80-(0*1)/-80-(0*1)/-80-(-5*6)/-811-(-8*6)/-8-6-(0*6)/-86-(-8*6)/-80-(0*6)/-80-(1*6)/-80-(0*6)/-80-(0*6)/-8 Result:BasisBx1x2x3x4x5x6x7x35/81010-1/800x6-3/2-64001/210x73/26-4001/201x43/801011/800F(X0)-15/45-6003/400 One more time make a calculation with 2nd row and x6 and 1st column and put x1 as a basis variable.BasisBx1x2x3x4x5x6x7x35/81010-1/800x6-3/2-64001/210x73/26-4001/201x43/801011/800F(X0)-15/45-6003/400θ -5/6- - - - - - Carry out transformations of the simplex table using the Gauss-Jordan method one more time:BasisBx1x2x3x4x5x6x7x33/802/310-1/241/60x11/41-2/300-1/12-1/60x700000111x43/801011/800F(X1)-50-8/3007/65/60Here’s all elements at basis columns > 0.Checking the optimality criterion - not optimal because there are positive coefficients in the index row.Definition of a new basic variable - x5 as the largest coefficient.Definition of a new free variable. min (- , - , 0 : 1 , 3/8 : 1/8 ) = 0. Therefore, the 3rd line is the leading one.BasisBx1x2x3x4x5x6x7minx33/802/310-1/241/60-x11/41-2/300-1/12-1/60-x7000001110x43/801011/8003F(X1)-50-8/3007/65/600 And one more time. Final simplex table will be like this:BasisBx1x2x3x4x5x6x7x33/802/31005/241/24x11/41-2/3000-1/121/12x500000111x43/801010-1/8-1/8F(X)-50-8/3000-1/3-7/6Checking the optimality criterion - Optimal!There are no positive values among the index string values. Therefore, this table determines the optimal solution for the problem.

Final solution. Here’s an optimal quantity of raw materials which can be used to create a necessary blend:

x1 = 0,25 kg;
x2 = 0 kg;
x3 = 0,375 kg;
x4 = 0,375 kg

Optimal price will be a result of function F(X) = 35*1/4 + 52*0 + 40*3/8 + 46*3/8 = 41 EUR

SAP implementation for LP Simplex solver

At the SAP system we have a class cl_genios_environment, this is a part of a package GENIOS_MAIN in GENIOS_FRAMEWORK (system component CA-EPT-GEN «GENeric Integer Optimizer System»).

Inside this class three solvers available:

MILP "GENIOS: Externer MILP Solver"
SIMP "GENIOS: internal simplex solver"
WEBS "GENIOS: WebService solver"

I’ve used a solver SIMP, this method execute all calculation according to Simplex method by standard ABAP code.

Proof of concept. ZFI_SIMP_LP_DEMO

Let’s create a simple SAP program to demonstrate how it works. It’s just a concept, so, I didn’t try to make a perfect ABAP coding…

Selection screen:

At selection screen I’ve put an all data related to raw materials (N/P/K percentage and price, highlighted in blue), but in real life you can use a real data from MARA/ MARD/ MBEW/ ACDOCA etc tables.

Also, target characteristics of a blend should be specified at selection screen (bottom part of the screen, red part):

Let’s run and check a result:

So, we get a correct optimal solution for this case.

Source code with comments:

*&---------------------------------------------------------------------*
*& Report ZFI_SIMP_LP_DEMO
*&---------------------------------------------------------------------*
*& Amelin A. 2024
* LP demo. Simplex solver. Find min BOM value
*&---------------------------------------------------------------------*
REPORT zfi_simp_lp_demo.

PARAMETERS:
  SolverID TYPE genios_solverid DEFAULT 'SIMP'.
PARAMETERS:
  p_pr1 TYPE i DEFAULT 35,
  p_n1  TYPE i DEFAULT 12,
  p_p1  TYPE i DEFAULT 12,
  p_k1  TYPE i DEFAULT 76.
SELECTION-SCREEN ULINE.
PARAMETERS:
  p_pr2 TYPE i DEFAULT 52,
  p_n2  TYPE i DEFAULT 20,
  p_p2  TYPE i DEFAULT 18,
  p_k2  TYPE i DEFAULT 62.
SELECTION-SCREEN ULINE.
PARAMETERS:
  p_pr3 TYPE i DEFAULT 40,
  p_n3  TYPE i DEFAULT 12,
  p_p3  TYPE i DEFAULT 18,
  p_k3  TYPE i DEFAULT 70.
SELECTION-SCREEN ULINE.
PARAMETERS:
  p_pr4 TYPE i DEFAULT 46,
  p_n4  TYPE i DEFAULT 20,
  p_p4  TYPE i DEFAULT 14,
  p_k4  TYPE i DEFAULT 66.
SELECTION-SCREEN ULINE.
PARAMETERS:
  p_nt TYPE i DEFAULT 15,
  p_pt TYPE i DEFAULT 15,
  p_kt TYPE i DEFAULT 70,
  p_tt TYPE i DEFAULT 1.

**********************************************************************
CONSTANTS:
  lc_modelname TYPE genios_name VALUE 'DEMO'.

**********************************************************************
START-OF-SELECTION.
  CHECK p_tt NE 0. "divide check
*Variables
  DATA:
    pr_1  TYPE genios_float,
    pr_2  TYPE genios_float,
    pr_3  TYPE genios_float,
    pr_4  TYPE genios_float,
    n_1   TYPE genios_float,
    n_2   TYPE genios_float,
    n_3   TYPE genios_float,
    n_4   TYPE genios_float,
    p_1   TYPE genios_float,
    p_2   TYPE genios_float,
    p_3   TYPE genios_float,
    p_4   TYPE genios_float,
    k_1   TYPE genios_float,
    k_2   TYPE genios_float,
    k_3   TYPE genios_float,
    k_4   TYPE genios_float,
    x_1   TYPE genios_float,
    x_2   TYPE genios_float,
    x_3   TYPE genios_float,
    x_4   TYPE genios_float,
    n_tot TYPE genios_float,
    p_tot TYPE genios_float,
    k_tot TYPE genios_float,
    tt    TYPE genios_float,
    lo_x1 TYPE REF TO cl_genios_variable,
    lo_x2 TYPE REF TO cl_genios_variable,
    lo_x3 TYPE REF TO cl_genios_variable,
    lo_x4 TYPE REF TO cl_genios_variable.


* 0) copy sscr data to float variables
  pr_1  = p_pr1.
  pr_2  = p_pr2.
  pr_3  = p_pr3.
  pr_4  = p_pr4.
  n_1   = p_n1.
  n_2   = p_n2.
  n_3   = p_n3.
  n_4   = p_n4.
  p_1   = p_p1.
  p_2   = p_p2.
  p_3   = p_p3.
  p_4   = p_p4.
  k_1   = p_k1.
  k_2   = p_k2.
  k_3   = p_k3.
  k_4   = p_k4.
  n_tot = p_nt.
  p_tot = p_pt.
  k_tot = p_kt.
  tt    = p_tt.

* Input data. Log
  WRITE: / |{ 'Source data:' }|.
  WRITE: / |{ 'Raw material 1: N-' && p_n1 && ';P-' && p_p1 && ';K-' && p_k1 && ';Price:' && p_pr1 }|.
  WRITE: / |{ 'Raw material 2: N-' && p_n2 && ';P-' && p_p2 && ';K-' && p_k2 && ';Price:' && p_pr2 }|.
  WRITE: / |{ 'Raw material 3: N-' && p_n3 && ';P-' && p_p3 && ';K-' && p_k3 && ';Price:' && p_pr3 }|.
  WRITE: / |{ 'Raw material 4: N-' && p_n4 && ';P-' && p_p4 && ';K-' && p_k4 && ';Price:' && p_pr4 }|.
  WRITE: / |{ 'Target blend: N-' && p_nt && ';P-' && p_pt && ';K-' && p_kt }|.
  ULINE.


  DATA:
    lo_env TYPE REF TO cl_genios_environment,
    lx_env TYPE REF TO cx_genios_environment,
    lv_msg TYPE string.

* 1) create a genios environment object
  lo_env = cl_genios_environment=>get_environment( ).

  DATA:
    lo_model TYPE REF TO cl_genios_model.
  TRY.
* 2) create a genios model (with a context-unique name)
      lo_model = lo_env->create_model( lc_modelname ).
    CATCH cx_genios_environment INTO lx_env.
      lv_msg = lx_env->get_text( ).
      WRITE: lv_msg, /.
      EXIT.
  ENDTRY.

* 3) fill the model with data
* 3.1) create the objective object
  DATA:
    lo_obj TYPE REF TO cl_genios_objective.
  lo_obj = lo_model->create_objective( if_genios_model_c=>gc_obj_minimization ).

* 3.2) create the needed variables
  lo_x1 = lo_model->create_variable( iv_name = 'x1' iv_type = if_genios_model_c=>gc_var_continuous ).
  lo_x2 = lo_model->create_variable( iv_name = 'x2' iv_type = if_genios_model_c=>gc_var_continuous ).
  lo_x3 = lo_model->create_variable( iv_name = 'x3' iv_type = if_genios_model_c=>gc_var_continuous ).
  lo_x4 = lo_model->create_variable( iv_name = 'x4' iv_type = if_genios_model_c=>gc_var_continuous ).

* 3.3) add the monom for the objective function
*      this is the coefficient for each variable in the objective function
  lo_obj->add_monom( io_variable = lo_x1 iv_coefficient = pr_1 ). "material price
  lo_obj->add_monom( io_variable = lo_x2 iv_coefficient = pr_2 ).
  lo_obj->add_monom( io_variable = lo_x3 iv_coefficient = pr_3 ).
  lo_obj->add_monom( io_variable = lo_x4 iv_coefficient = pr_4 ).

* 3.4) add the linear constraints with their monomes (coefficients for the variables
  DATA: lo_lin TYPE REF TO cl_genios_linearconstraint.

  lo_lin = lo_model->create_linearconstraint( iv_name = 'n' iv_type = if_genios_model_c=>gc_con_greaterorequal iv_righthandside = n_tot ).
  lo_lin->add_monom( io_variable = lo_x1 iv_coefficient = n_1 ).
  lo_lin->add_monom( io_variable = lo_x2 iv_coefficient = n_2 ).
  lo_lin->add_monom( io_variable = lo_x3 iv_coefficient = n_3 ).
  lo_lin->add_monom( io_variable = lo_x4 iv_coefficient = n_4 ).

  lo_lin = lo_model->create_linearconstraint( iv_name = 'p' iv_type = if_genios_model_c=>gc_con_greaterorequal iv_righthandside = p_tot ).
  lo_lin->add_monom( io_variable = lo_x1 iv_coefficient = p_1 ).
  lo_lin->add_monom( io_variable = lo_x2 iv_coefficient = p_2 ).
  lo_lin->add_monom( io_variable = lo_x3 iv_coefficient = p_3 ).
  lo_lin->add_monom( io_variable = lo_x4 iv_coefficient = p_4 ).

  lo_lin = lo_model->create_linearconstraint( iv_name = 'k' iv_type = if_genios_model_c=>gc_con_greaterorequal iv_righthandside = k_tot ).
  lo_lin->add_monom( io_variable = lo_x1 iv_coefficient = k_1 ).
  lo_lin->add_monom( io_variable = lo_x2 iv_coefficient = k_2 ).
  lo_lin->add_monom( io_variable = lo_x3 iv_coefficient = k_3 ).
  lo_lin->add_monom( io_variable = lo_x4 iv_coefficient = k_4 ).

  lo_lin = lo_model->create_linearconstraint( iv_name = 'total' iv_type = if_genios_model_c=>gc_con_equal iv_righthandside = 1 ).
  lo_lin->add_monom( io_variable = lo_x1 iv_coefficient = 1 ).
  lo_lin->add_monom( io_variable = lo_x2 iv_coefficient = 1 ).
  lo_lin->add_monom( io_variable = lo_x3 iv_coefficient = 1 ).
  lo_lin->add_monom( io_variable = lo_x4 iv_coefficient = 1 ).

* 4) as the model is filled, we now create a solver with a ID out of tx genios_solver (in this case, the default SIMPLEX solver)
  DATA:
    lo_solver TYPE REF TO cl_genios_solver,
    lx_solver TYPE REF TO cx_genios_solver.
  TRY.
      lo_solver ?= lo_env->create_solver( SolverID ).
    CATCH cx_genios_environment INTO lx_env.
      lv_msg = lx_env->get_text( ).
      WRITE: lv_msg, /.
      EXIT.
  ENDTRY.

* 4.1) load the model into the solver and solve it
  DATA:
    ls_result TYPE genioss_solver_result,
    lo_param  TYPE REF TO cl_genios_parameter.
  TRY.
      CREATE OBJECT lo_param
        EXPORTING
          iv_solver_id = lo_solver->get_solverid( ).
      lo_param->mv_timelimit = 300. " its a good idea to se a runtime - its only relevant for MILP runs, but ...

      lo_solver->load_model( lo_model ).
      ls_result = lo_solver->solve( lo_param ).
    CATCH cx_genios_solver INTO lx_solver.
      lv_msg = lx_solver->get_text( ).
      WRITE: lv_msg, /.
      EXIT.
  ENDTRY.

* 4.2) evaluate the results
  DATA:
    lt_variables   TYPE geniost_variable,
    ls_variable    TYPE genioss_variable,
    lv_primalvalue TYPE genios_float,
    lv_name        TYPE string,
    lv_index       TYPE string.
  IF ( ls_result-solution_status = if_genios_solver_result_c=>gc_optimal
     OR ls_result-solution_status = if_genios_solver_result_c=>gc_abortfeasible ).
* 4.3) found a solution => output the objective value as well as the variable values
    lv_primalvalue = lo_obj->get_value( ).
    WRITE: / 'Function to minimize'.
    WRITE: / 'F(x): ', |{ p_pr1 && '*x1+' && p_pr2 && '*x2+' &&  p_pr3 && '*x3+' && p_pr4 && '*x4 =>min' }|.
    WRITE: / 'Restrictions:'.
    WRITE: / |{ p_n1 && '*x1+' &&  p_n2 && '*x2+' &&  p_n3 && '*x3+' &&  p_n4 && '*x4 >=' &&  n_tot && '(x1+x2+x3+x4)' }|.
    WRITE: / |{ p_p1 && '*x1+' &&  p_p2 && '*x2+' &&  p_p3 && '*x3+' &&  p_p4 && '*x4 >=' &&  p_tot && '(x1+x2+x3+x4)' }|.
    WRITE: / |{ p_k1 && '*x1+' &&  p_k2 && '*x2+' &&  p_k3 && '*x3+' &&  p_k4 && '*x4 >=' &&  k_tot && '(x1+x2+x3+x4)' }|.
    WRITE: / |{ tt && '*x1+' &&  tt && '*x2+' &&  tt && '*x3+' &&  tt && '*x4 =' &&  tt && '(x1+x2+x3+x4)' }|.
    ULINE.
    WRITE: / 'Results:'.
    WRITE: /'Min price: ', |{ lv_primalvalue * tt }|.       "#EC NOTEXT
    lt_variables = lo_model->get_variables( ).
    LOOP AT lt_variables INTO ls_variable.
      lv_primalvalue = 0.
      lv_name = ls_variable-variable_ref->gv_name.
      lv_index = ls_variable-variable_index.
      lv_primalvalue = ls_variable-variable_ref->get_primalvalue( ).
      WRITE: / lv_name,' = ',|{ lv_primalvalue * tt }|.
      IF lv_name = 'x1'.
        x_1 = lv_primalvalue * tt.
      ELSEIF lv_name = 'x2'.
        x_2 = lv_primalvalue * tt.
      ELSEIF lv_name = 'x3'.
        x_3 = lv_primalvalue * tt.
      ELSEIF lv_name = 'x4'.
        x_4 = lv_primalvalue * tt.
      ENDIF.
    ENDLOOP.
    WRITE: / 'Final blend characteristics:'.
    WRITE: /  'N:' && |{ ( ( ( x_1 * p_n1 ) + ( x_2 * p_n2 ) + ( x_3 * p_n3 ) + ( x_4 * p_n4 ) ) / tt ) }| && '%'.
    WRITE: /  'P:' && |{ ( ( ( x_1 * p_p1 ) + ( x_2 * p_p2 ) + ( x_3 * p_p3 ) + ( x_4 * p_p4 ) ) / tt ) }| && '%'.
    WRITE: /  'K:' && |{ ( ( ( x_1 * p_k1 ) + ( x_2 * p_k2 ) + ( x_3 * p_k3 ) + ( x_4 * p_k4 ) ) / tt ) }| && '%'.
  ENDIF.
  ULINE.
* 4.4) output the solution status
  IF ( ls_result-solution_status = if_genios_solver_result_c=>gc_optimal ).
    WRITE: /,'Found solution is optimal'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_abortfeasible ).
    WRITE: /,'Solver aborted with a feasible solution'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_abortinfeasible ).
    WRITE: /,'Solver aborted with an infeasible solution'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_failinfeasible ).
    WRITE: /,'Solver failed due to infeasibility'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_solutionlimitreached ).
    WRITE: /,'Solution limit reached, but the a solution has been found'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_timelimitinfeasible ).
    WRITE: /,'Time limit reached and the solution is infeasible'.
  ELSEIF ( ls_result-solution_status = if_genios_solver_result_c=>gc_unknown ).
    WRITE: /,'Solution status is unknown'.
  ENDIF.

* 5) some cleanup
  IF ( lo_env IS BOUND ).
    lo_env->destroy_solver( SolverID ).
    lo_env->destroy_model( lc_modelname ).
  ENDIF.

SAP Document and Reporting Compliance Brazil: Atualizações no CT-e MDF-e

2024-04-08T20:00:31.977000+02:00

(English version here)

Olá pessoal,

O time de SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil entregou semanas atrás as atualizações nas soluções de Conhecimento de Transporte Eletrônico (CT-e) e Manifesto Eletrônico de Documentos Fiscais (MDF-e). As mudanças atendem à Nota Técnica 2024.001 versão 1.01 (Inclusão do Benefício Fiscal) de CT-e e à Nota Técnica 2024.001 versão 1.01 (Evento de Encerramento) de MDF-e da SEFAZ.

Nota Técnica 2024.001 versão 1.01 para CT-e e MDF-e

Conhecimento de Transporte Eletrônico (CT-e):

A nova atualização do CT-e (modelo 57) e CT-e OS (modelo 67) permite incluir os novos campos vICMSDeson (valor do ICMS desonerado) e cBenef (Código do Benefício Fiscal) nos arquivos XML. Esses campos serão incluídos nos seguintes grupos de ICMS: ICMS20, ICMS45, ICMS60, ICMS90 e ICMSOutraUF.

Você pode implementar as mudanças seguindo as instruções nas seguintes SAP Notes:

SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824
SAP Note 3441171
SAP Note 3445374

Você pode implementar as mudanças na solução SAP Electronic Invoicing for Brazil (SAP NFE) seguindo as instruções nas SAP Notes:

SAP Note 3426934
SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824

A Nota Técnica 2024.001 Versão 1.02 de CT-e foi revisada e não haverá impacto na solução de Conhecimento de Transporte Eletrônico (CT-e).

Consulte o SAP Knowledge Base Article 2807654 para obter informações sobre resolução de problemas.

Manifesto Eletrônico de Documentos Fiscais (MDF-e):

A atualização no MDF-e (modelo 58) permite incluir nos arquivos XML o campo indEncPorTerceiro, que foi introduzido no evento de encerramento (tipo 110112). Para implementar esta atualização, siga as instruções na SAP Note 3437854.

A Nota Técnica 2024.001 Versão 1.02 de MDF-e foi revisada. O schema XML foi atualizado em nosso serviço, não sendo necessária a implementação de outras SAP Notes para esta alteração.

Você pode implementar as mudanças na solução SAP Electronic Invoicing for Brazil (SAP NFE) seguindo as instruções na SAP Note 3431096.

Blog posts relacionados:

Para obter um passo a passo sobre como usar o SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil, consulte as seguintes páginas do portal SAP Help:

Você pode receber alerta por email quando novas SAP Notes forem lançadas ou atualizadas nos componentes listados abaixo; basta seguir as instruções do SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE
SLL-NFE

Acesse o gerenciador de modificações legais para ter uma noção do que está planejado para ser suportado. Consulte o SAP Knowledge Base Article 3421995 e a página “regulatory change manager” para entender como usar esta ferramenta.

Gostou desse post? Dê um Like (Kudos) e compartilhe o conteúdo com seus colegas. Sinta-se à vontade para deixar suas perguntas ou ler posts semelhantes no SAP Community do SAP Document and Reporting Compliance.

Para acompanhar as últimas notícias da NF-e, siga a tag SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) e a comunidade SAP Document and Reporting Compliance.

Obrigado e até a próxima,
Thiago

Be an Expert with PLM System Integration Support Content!

2024-04-09T08:43:37.263000+02:00

Recently, many of you have asked where to find detailed information on the setup of different integration scenarios via PLM system integration. As you know, PLM system integration enables a seamless transfer of product-relevant data between SAP S/4HANA or SAP ERP and an external PLM system, allowing for bi-directional process integration.

We are happy to inform you that you can now access a comprehensive set of support knowledge directly from the SAP Help Portal.

Start today and explore the PLM system integration expert content here. Enjoy

Best practices regarding configuration per object type
How-to information on the activation of our standard content via BC Sets
A closer look at error messages and what they tell you.

Also, learn how you can test your integration, even without an external PLM system in place.

Check out our our overview video to get a first glimpse!

Now, it's your turn to unleash the full potential of PLM system integration!

SAP Document and Reporting Compliance Brazil: Dashboard do Usage Analytics

2024-04-09T21:55:23.727000+02:00

(English version here)

Olá pessoal,

Lançamos uma nova funcionalidade que permite que você verifique sua utilização do SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil fornecendo informações mais precisas sobre o consumo.

Esse novo recurso só está disponível a partir do ano de 2024 para os IDs de métrica CY140 (faturamento de saída) e CY141 (faturamento de entrada). Para saber qual é o seu ID de métrica, verifique no SAP LUI (License Utilization Information) no app “SAP for Me”. Mais informações sobre SAP LUI estão descritas abaixo.

Você acessa o dashboard do Usage Analytics no painel de navegação esquerdo do SAP BTP Cockpit, como mostrado na imagem a seguir:

No dashboard do Usage Analytics, você pode encontrar informações sobre o produto "SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil" (inbound and outbound invoicing options for Brazil).

Para processos de saída (outbound), temos dois grupos de classificação, chamados Grupo A e Grupo B, como mostrado na imagem a seguir:

Para exibir todas as Usages na tela, deixe o filtro Service em branco. Nem todas as classificações estão sendo exibidas nesta imagem.

Grupo A: Classifica cada documento processado (definição de métrica) por tipo e ação. O Grupo A é composto pelos documentos abaixo.

Documentos processados (NF-e, CT-e, NFS-e, MDF-e e NF3-e)
Documentos de eventos processados (CC-e, cancelamento, inutilização, etc.)
Arquivos de documentos exibidos/baixados*
Arquivos de eventos exibidos/baixados*
Documentos reenviados para aprovação (NF-e, CT-e, NFS-e, MDF-e e NF3-e)

*Somente quando o mesmo arquivo XML for baixado pela segunda vez. Isso evita o mau consumo.

Acesse o Cloud (SaaS) Application Usage & SAP Business Technology Platform para verificar a lista completa de classificação do Grupo A.

Grupo B: Classifica cada documento processado (definição métrica) conforme o tipo de ambiente:

Documentos processados em ambiente produtivo.
Documentos processados em ambiente de homologação.

A soma dos documentos exibidos no Grupo A deve ser igual à soma dos documentos exibidos no Grupo B. O número total de documentos é exibido em Total documents from group A or B.

Considerando o exemplo da imagem anterior, a soma do Grupo A é 1317 e a soma do Grupo B também é 1317.

Para processos de fatura de entrada, também temos dois grupos de classificação, chamados Grupo A e Grupo B, como mostrado na imagem a seguir:

Para exibir todas as utilizações na tela, deixe o filtro Service em branco. Nem todas as classificações podem ser exibidas nesta imagem.

Grupo A: Classifica cada documento processado (definição de métrica) por tipo e ação. O grupo A é composto pelos seguintes tipos de documentos:

Documentos processados (NF-e, CT-e)
Documentos de evento processados (CC-e, cancelamento, etc.)
Arquivos de documentos baixados da SEFAZ (NF-e, CT-e)
Arquivos de eventos baixados da SEFAZ (CC-e, cancelamento, etc.)

Acesse o Cloud (SaaS) Application Usage e o SAP Business Technology Platform para verificar a lista completa de classificação do Grupo A.

Grupo B: Classifica cada documento processado (definição métrica) conforme o tipo de ambiente:

Documentos processados em ambiente produtivo.
Documentos processados em ambiente de homologação.

A soma dos documentos exibidos no Grupo A deve ser igual à soma dos documentos exibidos no Grupo B. O número total de documentos é exibido em Total document from group A or B.

Considerando o exemplo da imagem anterior, a soma do Grupo A é 202 e a soma do Grupo B também é 202.

Se você encontrar discrepâncias, certifique-se de que não haja codificação personalizada que chame o serviço em nuvem duas vezes ou crie um efeito de loop.

Principais opções da análise de utilização

Capability: no dashboard Usage Analytics, você pode usar o menu suspenso Capability para filtrar a utilização do serviço selecionando os recursos do SAP BTP (aplicativo, automação ou integração).
Service: nessa lista suspensa, você pode usá-la para filtrar o uso de cada plano de serviços na subconta da sua empresa. Por exemplo, você pode filtrar a utilização de dados da solução “opção de emissão de fatura de entrada e de faturamento de saída para o Brasil” (inbound and outbound invoicing options for Brazil).
Metric: você pode selecionar uma das métricas (documentos exibidos, baixados, reenviados para aprovação ou processados). Você pode utilizar o menu suspenso Metric para evitar exibir todos os documentos ao mesmo tempo.
Period: em relação ao intervalo de tempo selecionado no campo Period, esteja ciente de que as informações apresentadas são do ano 2024 em diante e somente após a instalação das seguintes SAP Notes.

Instalação

Você pode implementar essas modificações seguindo as instruções nas SAP Notes.

As SAP Notes são necessárias para fornecer os dados utilizados em métricas e para corresponder à quantidade do Grupo B aos dados de consumo no rótulo Total document from group A or B. A instalação das SAP Notes não tem impacto nos processos de cálculo da fatura atuais.

Outbound (faturamento de saída): SAP Note 3111469
Inbound (fatura de entrada): SAP Note 3399269

License Utilization Information (LUI)

O aplicativo License Utilization Information (LUI) fornece detalhes sobre a titularidade da licença e sobre a utilização do software. Para receber os resultados, uma medição do sistema é realizada em cada sistema relevante.

O dashboard Usage Analytics pode ser usado em conjunto com a LUI selecionando o mesmo período para gerar análises sobre como a solução SAP Document and Reporting Compliance está sendo usada. O painel do LUI deve mostrar o mesmo valor na coluna Measured e no Total document from group A or B do Usage Analytics.

A aplicação LUI pode ser acessada por meio do SAP for Me. Verifique o License Utilization Information para obter detalhes sobre como utilizá-las e acessá-las.

Data da contabilização

A data da métrica pode não representar a data da ação do usuário. Por exemplo, podem existir discrepâncias em que um documento processado no fim de um mês aparece no consumo do mês seguinte, devido ao processo assíncrono da contabilização. O momento em que um usuário realiza uma ação e quando essa ação é refletida em nossas métricas pode nem sempre se alinhar perfeitamente, especialmente na transição entre os dias.

Você pode entrar em contato com seu executivo de contas se tiver perguntas sobre os valores ou se precisar de mais ajuda. Verifique a SAP Note 2626344.

Você pode receber alerta por email quando novas SAP Notes forem lançadas ou atualizadas nos componentes listados abaixo; basta seguir as instruções do SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE

Para acompanhar as últimas notícias da NF-e, siga a tag SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) e a comunidade SAP Document and Reporting Compliance.

Obrigado e até a próxima,
Bruno Eltz e Thiago Cezimbra

Tags: brasil, einvoice, einvoicing, e-invoicing, electronic invoice, electronic invoicing, edocument, edoc, e-document, e-docs, e-doc, e-docs, drc, document compliance, nota fiscal eletrônica, electronic nota fiscal

Join and innovate with the SAP Enterprise Support Advisory Council (ESAC) Program

2024-04-11T10:43:38.796000+02:00

co-author: Bruno Cherqui

The SAP Enterprise Support Advisory Council provides immense value by bringing together a select group of customers to collaborate with SAP experts and provide valuable insights and feedback on the development, improvement, and optimization of the SAP Enterprise Support program. Through this collaboration, members have the opportunity to influence SAP's support offerings, gain early access to new tools and resources, and actively shape the future direction of SAP's support solutions.

The program is open to all SAP Enterprise Support customers at no additional cost (but limited capacity) and is covering all major SAP cloud solutions such as SAP S/4HANA, CX, BTP, SAP SuccessFactors HCM, ISBN, Cross Solutions topics.

New open workstreams for Q2:

Continuous Quality Check (CQC): Transformation Assessment for Sustainability
Continuous Quality Check (CQC): Transformation Assessment for SAP Integrated Business Planning
Continuous Quality Check (CQC): Deployment Readiness for SAP SuccessFactors HCM Suite EXPANSION
Expert-guided Implementation (EGI): SAP Datasphere Fundamentals (Data and Analytics)

Find an overview of all our workstreams running in Q2 here.

To express interest, ask a question or join the program: contact us via esac@sap.com.

For more information you can also refer to our ESAC landing page on the SAP Support Portal.

Your SAP Enterprise Support Advisory Council team

esac@sap.com

What You Need to Know: Security and Compliance when Moving to a Cloud ERP Solution

2024-04-15T15:56:19.392000+02:00

According to the IDC Info brief, Trusted ERP Systems: Priority offerings in security, privacy, compliance and ESG, trustworthy businesses feature a robust approach to risk management, security, compliance, privacy, and ESG.

In fact, the top reasons for moving to a cloud ERP system include better security, compliance, privacy, and risk posture (45%) and better alignment with company values/ESG initiatives (34%).

Yet, moving to a SaaS model carries a shift in both compliance and security-related responsibilities when compared to on-premise deployments.

These topics will be the major topic of discussion of an upcoming webinar, Secure your Success: Security, Compliance, ESG on April 24th.

Here are some of the key questions that will be addressed:

What are the strategies to protect sensitive data?

All too often, we hear about data leaks of personal and company data, third parties infiltrating and influencing social media, all the way up to election interference.

It’s obvious that no one wants their customer or intellectual property data leaked online. But it is a constant challenge for companies to ensure protection of data in the face of ever increasing and creative threats.

This is why it is critical to have a secure business system that takes care of cyber security as part of its standard practices. From secure authentication of users, secure access rights based on business roles and responsibilities and auditability of activity trails throughout and across business processes.

How do you comply with regulations?

We are increasingly seeing rules and regulations being implemented and enforced across regions and industries and at individual country levels. For example, at last count there were over 600 Environmental, Social & Governance (ESG) rules in place around the globe. And these can result in financial penalties, not to mention loss of brand representation and investment dollars.

Keeping up with changing tax accounting and reporting rules, and the ever-increasing sustainability regulations (e.g. plastics taxes) can become a headache for companies of all sizes. And having a cloud ERP provider that can support and protect you against these evolving regulations, especially as you grow into new markets, industries or regions of the world, enables you to focus on where your core competencies are.

How can you minimize and mitigate cyber threats?

Unfortunately, if you don’t have a cyber threat defensive strategy, hackers will take advantage. As with our personal life where no one uses their computer without anti-virus, we should be thinking the same with our business life and no one should deploy an ERP solution without a cyber defense strategy.

It is important to partner with a systems provider and partners that can provide this protection. Ask for the BS 100012 or similar personal information management certificate. Ask to see the System and Organization Controls (SOC) reports. Ask why you should trust them with your mission critical and sensitive data.

As your company grows, managing increased processes and data volume becomes crucial for maintaining performance and customer satisfaction. H. Kracht's Erben AG, a Swiss company in hotels and wine, faced these challenges. Transitioning to a public cloud ERP, SAP S/4HANA Cloud Public Edition as part of their GROW with SAP initiative helped them reduce hardware costs and ensure continuous security updates. Now, they efficiently manage processes, data collection, and data protection for peace of mind.

Where to learn more

Please join us at the Secure your Success: Security, Compliance, ESG webinar on April 24th.

This session will provide an overview of the capabilities SAP brings to simplify these activities, as well as understand the role of both the customer and the SaaS provider when it comes to compliance responsibilities. You'll understand the capabilities SAP delivers as it pertains to security, audit, data privacy and protection, and regulatory compliance. Furthermore, you'll learn how H. Kracht's Erben AG trusts SAP to protect their server farms while maintaining top performance!

Field Status Variant & Field Status Group

2024-04-16T12:41:01.750000+02:00

Define Field Status Variant ?

The field status variant it contains the list of field status group.

The field status variant defines at the client level and can be assign to multiple company codes.

Field Status Group:

It contains the grouping of the fields and the each field it contains the status of the field that is suppress, required and optional.

The field status groups need to be assign in the GL Account company code segment data tab.

The field status group in GL Account ,it controls the data entry filling at the line item level while posting the transactions to the GL Account.

The field status group it controls which data entry fields are requires, optional, not required ( suppress) while posting to the G/L Account.

The document entry fields can be controlled in two ways.

1. Field status group in GL Account

2. Field status in posting key.

Both field stature groups in GL account and field status in posting key can be control field status of the document entry.

SPRO -> SAP Reference IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Define Field Status Variant (OBC4)

Data Was Saved in Table of T004V

Below are SAP predefined field status Groups

We can use for the below category of GL accounts

YB01 – GENERAL

This group can be used for any type of GL Accounts and all the fields status contains optional

YB03-MATERIAL CONSUMPTION ACCOUNTS

The group can be used for all material consumptions GL Accounts

Example :RM Consumption Accounts, PM Consumption Accounts etc.

YB04-COST ACCOUNTS.

The group can be used for all overhead expenditure GL Accounts

Example :Salaries GL , Rent GL , Travelling Exp GL etc.

YB05-BANK

This group can be used for bank related GL Accounts

Example :Bank GL , Outgoing Payment ( Check issue GL) , Incoming Payment GL ( Check Deposit GL)

YB06-MATERIAL ACCOUNTS

This group can be used for balance sheet inventory or stock related GL

Example :Stock-RM STOCK-FG, Stock-SFG etc.

YB07-ASSETS ACCOUNT

This group can be used for fixed assets GL Accounts

Example: Building GL , P&M GL, Furniture GL , Vehicles GL etc.

YB12- RECIEVABLE /PAYABLES CLEARING

This group can be used for bills payable GL Accounts and bills receivables

Example :Debtors control GL ( Bills receivable GL), Creditors control GL ( Bills payable GL account) etc.

YB26- ACCOUNTS FOR DOWN PAYMENT MADE

This group can be used for advance paid to vender GL Accounts.

Example :Advance to Vendor GL

YB29-REVENUE ACCOUNT

This group can be used for all sales and revenue related GL Accounts

Example :Sales , Misc Sales GL

YB31-ACCOUNT FOR DOWN PAYMENT RECEIVED-(ADVANCE RECEVED FROM Customers)

This group can be used for advance received from customer GL

Example :Advance from Customer GL

YB41- TAX OFFICE CLEARING A/C

This group can be used for tax payable Accounts

Example :Sales Tax payable , GST Payable ,VAT payable , Service Tax Payable GL

YB45-GOODS / INVOICE RECEIVED CLEARING A/C – (GR/IR)

This group can be used for GR/IR clearing GL accounts

Example :GR/IR Clearing GL

Below procedure followed in procurement process

1. At the time of Goods received from Vendor to Stock

Dr Stock

Cr GR/IR Clearing GL account ( Intermediate GL account)

2. At the time of Invoice received from Vendor

Dr GR/IR Clearing GL account ( Intermediate GL account)

Cr Vendor X

SECC-Secondary GL

This Group can be used for all Secondary GL accounts

Note: required only in S/4 HANA , Not required in ECC

Assign Company Code to Field Status Variants

SPRO -> SAP Reference IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Assign Company Code to Field Status Variants (OBC5)

Data was Saved in the Table of V_001_P

Retained Earnings Account

2024-04-18T12:46:26.601000+02:00

Retained Earnings Account:

At the end of the fiscal year, We need to carry forward the balance of the p\L account to the retained earnings accounts( BS General Reserve Accounts).

The profit & loss statement account type it represents the retained earnings account.

The retained earnings account can also be called as net profit/net losses carry forward to be the part of the general reserves account.

The profit & loss statement account type can be defined similar to variant.

We can define more than one profit &loss statement account type per COA.

If we can define the more than one profit &loss statements account type for chart of account then we need to assign profit & loss statement account type in the G/L master for every profit &loss account.

If we define single profit &loss statement account type for COA , in this case all profit & loss accounts by default assign to the profit & loss statement account type.

Not required to assign manually in the G/L account.

The profit & loss account need to be defined for each COA wise.

Profit & loss statement account type can be defined maximum upto 2 digit code.

We can use more than one retained earnings GL account per Chart of Account if you are using the Account Approach to address the different Accounting Principles.

Examples:

X1 P&L statement Account Type for Common Accounts

X2 P&L statement Account Type for USGAP

X3 P&L statement Account Type for IFRSGAP

X4 P&L statement Account Type for IAS GAP

Note:

Not Required Multiple Retained earning accounts per Chart of Accounts if you are following Ledger Approach.

Why multiple retained earnings account required ?

We have two approaches to address the different accounting principle requirements

Approach1=======> Account Approach Approach2=========> Ledger Approach

Approach1=======> Account Approach:

We will open few additional GL accounts in addition to common GL accounts for specific to accounting principle wise for those areas need to treat differently

IFRS	COMMON GL	USGAP
25 GL accounts for specific to IFRS	300 Common GL accounts	22 GL accounts for specific to USGAP

FS(Financial Statement) for IFRS =IFRS specific GL accounts + Common GL accounts

FS(Financial Statement) for USGAP =USGAP specific GL accounts + Common GL accounts

In Account approach , We will maintain more than one Retained earnings Accounts

In the above example ,

X1 ==> Retained earning accounts -common ==> Assigned to all common P&L GL accounts

X2 ==> Retained earning accounts -IFRS Accounts ==> Assigned to IFRS specific GL accounts

X3 ==> Retained earning accounts -USGAP Accounts ==> Assigned to USGAP specific GL accounts

Approach2=========> Ledger Approach:

Each Ledger represents the one set of Books

Ledger ==>L2===========> USGAP

Ledger ==>L1===========> IFRS

In the ledger approach , not required to maintain additional GL accounts for specific to accounting principle wise

Hence not required multiple retained earnings GL accounts ====> One retained earnings GL account is sufficient

Create Retained Earnings Account:

Need to be Defined P&L statement account type per Each Chart of Account wise

Operational COA(RELP)

X1 P&L Statement A/ Type for Op COA ( RELP )

Grp COA (RELG)

G1 P&L Statement A/ Type for Grp COA ( RELG )

Country COA (RELC)

N1 P&L Statement A/ Type for Country COA ( RELC )

SPRO -> SAP Reference IMG -> Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Preparations -> Define Retained Earnings Accounts (OB53)

Data was Saved in the Table of T030

Jumpstart your cloud ERP journey with guided enablement in RISE with SAP Methodology

2024-04-25T14:15:04.009000+02:00

Transform with confidence using RISE with SAP Methodology. Today we're introducing an improved customer onboarding experience and quality check enhancements in the RISE with SAP Methodology. All customers subscribing for the first time to RISE with SAP after April 1, 2024, will go through this improved experience at no additional cost. The new experience provides guided enablement and related tools and services to help customers implement their cloud ERP solutions with clarity and confidence. This experience brings focus to clean core mindset and simplifies best practice implementation of clean core by making it a more central, actionable and measurable standard of all implementations. This ensures that all customers benefit from business agility, faster innovation cycles, and improved value realization.

The announcement articulated two main areas of new investments SAP is making and which are the following:

Expert onboarding guidance through embedded launch activities: To share best practice guidance that we have learned over thousands of successful RISE with SAP customer implementations, each SAP customer will be assigned dedicated SAP adviser who delivers 1:1 and 1:many enablement sessions educating customers on the RISE with SAP methodology, clean core strategy and related tools for implementation.
‘Clean core’ focused success plan and quality checks: We are augmenting the methodologies and tools to include new project roadmaps, ’clean-core’ success plans and quality gates aligned with best practices for successful implementation and unlocking business value faster. Learn More

In this blog post, we are providing you with more details on the first area of the new onboarding experience offering to customers through embedded launch activities.

What are the Embedded Launch Activities?

Embedded launch activities are built to prepare customers for RISE with SAP with SAP S/4HANA Cloud Private Edition engagement by providing insights on global best practices. Through this early enablement, we want to ensure that customers feel supported on their Cloud ERP journey and proceed with clarity and confidence. Each RISE with SAP customer is now assigned a dedicated SAP Advisor who helps customer navigate the implementation roadmap and provides education on the overall journey, RISE with SAP methodology, the clean core strategy and initial set up of tools and services. In addition, customers have access to several recorded enablement sessions to go deeper on these topics and be prepared for the journey ahead.

Initial Advisor led 1:1 Sessions: The journey kicks off with three personalized 1:1 customer-facing calls delivered by the SAP assigned Advisor. These initial calls are designed to prepare the customer for the upcoming implementation phases and include topics such as introduction to the RISE with SAP Methodology, the clean core strategy and provision the Cloud ALM tool which will be used to track and report on the actual project implementation. The onboarding experience has renewed focus on implementing a clean core and therefore a primary outcome of the 1:1 sessions is to agree on setting up a clean core success plan which is available as project tasks in Cloud ALM tool for tracking and reporting throughout implementation. Another key outcome is the initiation of clean core based `Quality Gate` which is a checkpoint to ensure customer is implementing in alignment with SAP recommended best practices before proceeding to next project phase.

Additional 1:Many Sessions: After the 1:1 sessions, there are additional four sessions as a continuation of the embedded launch activities that are aimed at guiding customers through each phase of their project implementation, offer practical insights and best practices. Those sessions include

Project Readiness – Get ready to start your implementation, learn how to run your solution by leveraging SAP best practices.
Project Guidance – Progress with your implementation. Access available SAP resources and tools to save implementation.
Project Progress – Monitor your project progress. Safeguard the success of your implementation using SAP services included in your contract.
Go-Live Preparation – Get ready for successful Go-live! Check your go-live readiness with our SAP support and services. Prepare post go-live activities and continue your innovation plan.

Recorded Enablement Sessions: In addition to the 1:1 and the 1: many advisor-led sessions, customers also have access to a collection of role-based, recorded enablement sessions covering business process leading practices, solution architectures and other strategic topics. SAP S/4HANA Cloud private edition embedded launch activities include:

Conversion – For IT Leads
Conversion – For Project Teams
Activities For Business Users
New Implementation – For IT Leads
New Implementation – For Project Team

Through these embedded launch activities, our goal is to empower you to get started with your cloud ERP journey with all the knowledge and resources required to be successful.

To learn more, please see the SAP News Announcement and join us for our upcoming webinar on May 23rd where we will go deeper into this new onboarding experience in RISE with SAP Methodology! Register here.

Unleash the power of Business AI across your Cloud ERP environment!

2024-05-03T20:08:41.484000+02:00

It’s safe to say that AI is everywhere. It’s often a case of “the answer is AI, what’s the question”?

The reality is that business landscapes are rapidly evolving, driven by innovative technologies like Cloud ERP and Business AI.

The business data now available in Cloud ERP systems, complimented by unstructured data from external sources provide a foundation to change the way we make decisions, empower users, automate processes, and predict the future.

Trust in the data and AI recommendations

But AI is only as good as the data it is analyzing.

SAP’s customers provide products that run the world, from baby milk formula to the vehicles that move us from place to place. They look for business systems that help them grow, predict, and adapt to risks, opportunities, and ever-changing business dynamics. And they need to be confident that the decisions they make based on AI generated insights and recommendations are accurate and informed.

Wouldn’t you want AI from someone who has decades of experience of running serious businesses and business processes?

Welcome to Business AI

Business AI leveraging machine learning and natural language processing, analyses this data to generate insights and automate tasks.

This powerful combination of Cloud ERP and Business AI empowers businesses to transform operations, gain deeper insights, and make data-driven decisions with unprecedented accuracy.

As Deloitte’s Subit J. Mathew explained in a recent Future of ERP podcast, “ERPs of the future will be composable, and what makes them composable is a robust foundation like SAP, steering it with human creativity and powering it with AI and intelligent technologies. Essentially moving us from human augmentation to human automation as time progresses.”

With SAP Business AI, we build the system of intelligence with three core principles:

Relevant: Everything is embedded into our leading enterprise applications and business technology solutions. Customers can count on their SAP systems to be futureproofed with the most relevant AI experiences in the context of their business.
Reliable: Based on the unique business data AND business process context, we can deliver the most reliable business AI. Your AI is only as good as your data – we have the most important data and the only one with business data context intact.
Responsible: We deliver AI with the highest levels of concern for security, privacy, compliance, and ethics. SAP has the right character to deliver AI responsibly. Ironically, the more responsibly one builds AI technology, the freer an organization is to use it.
Creating an AI Business Strategy
This underscores the necessity for businesses to thoroughly assess and comprehend various related aspects to craft a robust AI Business Strategy. The key is to identify your business challenges you need to address, the use cases that will improve your business, and then determine how best to address them.
The possible applications for AI in the business context seem endless, but how do you turn this potential into tangible value? What scenarios will work best for your business? How do you build an AI strategy? And how will AI align with your specific operational requirements?
As Subit explained in the podcast, “AI is really about doing things that you do today differently, and being able to do different things that you could never do before!”
We discussed how companies need to segment their AI strategies into three distinct categories:
- Improve efficiency to do the things it does today in a different, more accelerated fashion.
- Improve the user experience to become more intuitive and provide contextual information.
- Deliver new processes and innovation previously not had in the organization.
  A lot of companies are looking at establishing AI Center of Excellence, which really look at it from multiple perspectives and involves answering several questions:
  What is the right governance model you want to put in place around what initiatives do you even prioritize?
  - How do you prioritize the use cases you want to go after?
  - How do you quantify the value of what you want to go after?
  - What is the technology fabric that you're going to use to accomplish this?
    This is the value of where an ERP platform such as SAP comes in. If you combine them with some of the large language models out there, it opens itself up to doing remarkable things.
    To learn more, listen to the Future of ERP podcast: Generative AI and ERP with Deloitte’s Subit Mathew.
    And join us at the upcoming Sapphire and ASUG Annual Conference in Orlando on June 3rd - 5th where you will discover the power of Business AI for Cloud ERP that’s reliable, relevant to your business, and responsible by design.

SAP S/4HANA - Extracting User Email Addresses from Standard Tables

2024-05-10T15:09:30.362000+02:00

What are we discussing here?

When working with SAP systems, it is fundamental to need / verify user email addresses for various purposes. Whether it is to send Automated Notifications, facilitating communication between users, or Generating Reports, having accurate and up-to-date email addresses is crucial. However, extracting the email address from SAP system is not as easy as we think. In this blog post, we will explore the simplest method to extract / find email addresses of users from SAP Standard tables.

Note : There is no direct transaction code or program to extract email addresses of users

How are we going to achieve it?

The primary table that stores user information in SAP is USR21. This table contains User Master Data, including Personal Numbers (PERSNUMBER) associated with each user. To retrieve email addresses, we will link this table with the address data table ADR6.

What is USR21?

USR21 is a standard table in SAP ERP system that assigns User Names and Address Keys.

What is ADR6?

The ADR6 table in SAP ERP system is a standard table that stores email addresses (Business Address Services) for any address record.

Procedure to Extract Email Address from SAP Tables

Execute table view transaction code: SE16 -> Enter Table Name : USR21 -> Execute

Provide the list of User ID(s) through Multiple Selection for BNAME -> Execute

Copy the list of Personnel Number (PERSNUMBER) for the users

Execute table view transaction code: SE16 -> Enter Table Name: ADR6 -> Execute

Provide the list of Personnel Number(s) through Multiple Selection for PERSNUMBER -> Execute

SMTP_ADDR column of ADR6 table will provide the list of email address for users

SAP also offers to extract the list into Spreadsheet from this screen

Tip : Ensure to select ALV Grid Display in User Specific Settings at initial screen of ADR6

What are other options?

Another approach for SAP S/4HANA is to leverage the built-in Core Data Services (CDS) view.

Table : PUSER002 can also be used | BNAME = UserName | Ensure column SMTP_ADDR is visible

Word of Caution

Avoid Unintended Disclosure

When querying SAP tables, be cautious not to inadvertently disclose email addresses to unauthorized users or external sources.

Limit access to relevant personnel and follow proper authorization procedures.

Remember, accurate and secure email addresses contribute to smooth business processes and effective communication within your organization. Handle them responsibly, and always prioritize data protection.

If you have any further questions or need assistance, do not hesitate to comment on this blog. Happy SAP querying!

Feel free to share this article with your colleagues and peers who work with SAP systems.

SAP Integration with SuccessFactors Through CPI: A Step-by-Step Handbook for Seamless Connectivity

2024-05-14T10:33:22.921000+02:00

Introduction:

This blog focuses on integrating SAP ERP with SuccessFactors through CPI, particularly addressing the configurable or standard Integration-Flow. Whether setting up initial connectivity with SAP or updating connectivity to a new SAP server, the steps outlined in this blog remain consistent across different SAP landscapes.

This blog will cover building the two-way communication channels:

SAP ERP to CPI Suite
CPI Suite to SAP ERP

Step :1 – Navigate to the CPI Suite and Copy the Name of the Integration Flow (I-Flow).

For Example: “Replicate Employee Master Data and Org. Assignments from SAP SuccessFactors Employee Central to SAP ERP or SAP S4HANA”

Step:2 – For all configurable Integration Flows (I-Flows), you can access the technical integration settings guide on the SAP Help Portal. Simply search on Google using the keyword "I-FlowName.pdf" to locate the relevant documentation.

For Example: “Replicate Employee Master Data and Org. Assignments from SAP SuccessFactors Employee Central to SAP ERP or SAP S4HANA.PDF”

This URL is applicable to the current situation https://help.sap.com/doc/2b73e3be50474cdc8cce76c3ff4860b6/2311/en-US/SF_EC_S4_Org_Objects_HCI_en-US.pdf

Under the "How to find Endpoint" section, locate the "Search Service definition." There, you'll find two procedures outlined in the SAP guide. Follow the steps provided in the guide accordingly.

1st Procedure - SAP ERP Communication to CPI:

Tips: Search for "SOAMANAGER" or "SM59" within the PDF guide to find the relevant web service definitions.

Step:3- Configure the URL in I-Flow Receivers

Step:4- Paste the URL into the Address section of the relevant Receiver.

2nd Procedure - SAP ERP Communication to CPI:

Tips: Look up "SOAMANAGER" or "SM59" in the PDF guide to find the relevant procedures.

Step:1 – Deploy the I-Flow

Step 2 - Copy the Endpoint URL or WSDL from Manage integration Content

Step 3 – Proceed to SOAMANAGER and Enter CPI SID in Username and Password

Then, navigate to the Transport Settings tab and enter the CPI Endpoint WSDL/URL.

Conclusion:

In conclusion, establishing seamless integration between SAP ERP and SuccessFactors through SAP Cloud Platform Integration (CPI) is critical for optimizing business processes and ensuring data consistency across the organization. This blog aims to provide a standard and comprehensive guide for configuring two-way communication regardless of the specific Integration flow (I-Flow).

Busting the Top 3 Myths about Cloud ERP Implementation

2024-05-20T13:34:48.273000+02:00

An Enterprise Resource Planning (ERP) implementation can revolutionize all aspects of your business processes. Let’s dive into the top three common myths associated with ERP implementation and discover the truths behind them.

#1 Myth: ERP is for large enterprises.

When people think about ERP applications, they often assume that only large or multinational enterprises implement these solutions. The truth is quite different than this.

For years, small and medium-sized enterprises (SMEs) remained on the sidelines, while their larger competitors enjoyed the advantages of ERP systems. However, times have changed, and the latest research tells a different story - around 80% of SAP’s customers are small and midsize companies, choosing SAP solutions that help them simplify, automate, and grow their businesses.

Resistance to change can complexify and prolong the process in both large multinational companies and SMEs. What businesses should understand is that a successful ERP implementation is an ongoing journey of continuous improvement.

No matter how you turn it, implementing ERP is an extensive project and requires careful planning. Fortunately, SAP tools like Digital Discovery Assessment (DDA) and Cloud Application Lifecycle Management (CALM) assist customers throughout the transition.

#2 Myth: Cloud ERP is less secure than on-premises.

On-Premise solutions have become a cornerstone in organizations’ technological infrastructure around the world. Given its long-standing tenure, the thinking often results in believing that on-premises are more secure. In reality, major cloud data centers have stronger security measures due to dedicated teams solely focused on guarding against security breaches.

Cloud providers offer a diverse array of security features and services aimed at assisting businesses in safeguarding their data and applications. Utilizing a cloud ERP system allows businesses to enhance their security posture without having to invest in their own security infrastructure as in on-prem users.

Ten years ago, CIOs may have been hesitant to move to the cloud due to the uncertainty in stable safeguarding, but now we see a shift towards embracing the cloud for its enhanced security features. Cloud providers handle the distribution and implementation of patches, ensuring that the business can operate without interrupting the business.

Moving to the cloud is not just a technical process, but a transformative one that keeps businesses current, up to date, and secure.

#3 Myth: ERP is a one-size-fits-all solution.

Most companies out there are struggling with a ‘spaghetti’ ERP landscape, hindering their ability to rapidly decode and transform to meet ever-changing business requirements. Businesses see the transformational benefits of implementing a fit-to-standard approach to ERP, which helps maintain a clean core while leaving complexity behind. However, it is important to note that ERP is not a one-size-fits-all solution, and deviations from standardization occur for a reason.

Within the organization, it is essential to establish a clear understanding that cloud ERP doesn’t require businesses to adopt a complete fit-to-standard approach. 90% of fit standard approach and the rest focused 10% serve as a competitive edge or a key to enhancing operational efficiency.

An example of a successful cloud ERP implementation is La Moderna, a food manufacturer in Mexico City. Their proactive adoption of best practices and simplification of processes has positioned them well to take advantage of future innovations in the ERP solution. The company’s attitude toward change management with a solid cloud ERP strategy enabled La Moderna to drive out complexity and positioned themselves to take advantage of the innovations in the solution.

Cloud ERP enables businesses to stay compliant with the evolving rules and regulations, as localization extends beyond language or currency considerations but also encompasses compliance with local regulations.

To learn more, please join us at the Secrets to Successful ERP Implementation webinar on May 22nd.

This session will provide an overview of the capabilities SAP brings to help you implement ERP successfully with confidence. Shifting from a blueprint and design approach to a fit-to-standard approach comes with many efficiencies and advantages, and you’ll understand the key to implementing your ERP successfully from our expert. Furthermore, you'll learn how La Moderna successfully implemented our Cloud ERP smoothly and realized its value quickly.

How to replicate your Fiori Inbox in Microsoft Teams

2024-05-20T15:11:28.256000+02:00

Using Looply you can replicate your Fiori Inbox in Teams, and it’s fast and easy.

Putting outstanding workitems in the face of those users who are not logged into SAP Work Zone / Fiori LaunchPad / SAPGUI can accelerate processes and lead to a host of other benefits.

We can build the solution in 4 steps.

[1] Consider the trigger points.

You have options. You might run a background job periodically to update Teams. This is easy to set up, but resource-intensive if you decide to run it every few minutes instead of, say, twice per day.

You could trigger the Teams card from SAP workflow, so that you can be sure that the card is updated when a workitem is created and/or completed. This would mean adding tasks to each workflow, so it’s considerably more work, but much less resource intensive, as there is no background job to run.

You could trigger the Teams card from SAP events – in exactly the same way that workflows are triggered, so that each time a critical workflow is triggered then the Teams card is created or updated. This is less work to set up, but potentially more complex because you might be triggering the Teams card before the workflow has determined the user. (So you might want to build in a 60-second wait.)

Of course, you could choose more than one approach, as some processes are more critical than others. For example, you might trigger a card update at the end of specific workflow processes, and also schedule a job twice a day.

In this example we’ll write a simple ABAP program to schedule as a background job. (See step 4.)

[2] Build your Looply Workflow.

Pure notification workflows tend to be very simple, as basically Looply is being passed some data, which it is mapping to Teams card fields, and push the card to the identified user.

In this example we’re going to add a button to enable the user to remove the card, and also the capability to either CREATE a new card where one doesn’t exist, or UPDATE an existing card.

This way there will never be more than one notification card for a user.

Let’s break this down.

When the workflow is triggered (and no existing card is in place) then the first step is to trigger a new card.
The card could be closed manually (‘MS Teams Response’) or it could be subsequently updated from another SAP call (‘External Response')
For the ‘External Response’ we need to capture the new data and push it into the data schema (‘payload’) that the card is mapped to. We do this mapping in the ‘Override Payload’ step.
Then we Update the card, using the new data.
Again, the user could close the card manually, or more data might be received from SAP. If more data is supplied then we update the schema from the data returned, and loop back to where we update the card.

[3] Build your Adaptive Card in Looply

The card is really simple as there are very few variables. It is basically a list of actions with URLS / deep links to point back to Fiori Inbox items.

This card comprises 5 containers, which are used to group and style fields:

Heading
User name
Item count
Item table
Action buttons

The item table has just one field, for description, which is bound to “[${wi_text}](${wi_full})” such that the workitem text (wi_text) is displayed with the URL to the Workitem for action (wi_full).

[4] Build the SAP trigger

There are two parts to this. Firstly the Process Determination table should be configured, adding the Looply workflow ID.

Secondly, the trigger program:

Here we have created a simple selection screen just with the user name as the selection option.

The program logic is:

For each selected user:

Get details using BAPI_USER_GET_DETAILS
Get inbox items using SAP_WAPI_CREATE_WORKLIST
For each item, build the URL to the workitem in Fiori Inbox
Prepare data fields for the card in an internal table
Read the Looply Process Determination table
Trigger Looply workflow using /LOOPLY/CORE=>TRIGGER_WF for Outbound Scenario. This tries to start a new workflow for the user, but fails if there is already a workflow running.
If that fails trigger Looply workflow using /LOOPLY/CORE=>TRIGGER_WF for Resume Scenario.

This will continue the Looply workflow from the current step.

*&---------------------------------------------------------------------*
*& Report Z_LOOPLY_INBOX_DEMO
*&---------------------------------------------------------------------*
*& Demo code only
*&---------------------------------------------------------------------*
REPORT z_looply_inbox_demo.

TYPES: BEGIN OF ty_card_items,
         workitem TYPE string,
         wi_full  TYPE string,
         wi_text  TYPE string,
       END OF ty_card_items.

TYPES: tty_card_items TYPE TABLE OF ty_card_items WITH NON-UNIQUE DEFAULT KEY.

TYPES: BEGIN OF ty_card_data,
         user  TYPE string,
         name  TYPE string,
         email TYPE string,
         count TYPE string,
         items TYPE tty_card_items,
       END OF ty_card_data.

DATA: ls_card_items     TYPE ty_card_items,
      lt_card_items     TYPE TABLE OF ty_card_items,
      ls_card_data      TYPE ty_card_data,
      lv_items          TYPE i,
      lt_usr01          TYPE TABLE OF usr01 WITH HEADER LINE,
      ls_usr01          TYPE usr01,
      lv_subrc          TYPE sysubrc,
      lt_worklist       TYPE TABLE OF swr_wihdr,
      ls_worklist       TYPE swr_wihdr,
      lv_data           TYPE string,
      ls_looply_trigger TYPE /looply/activity,
      lv_process_id     TYPE /looply/process_id,
      lv_recipient      TYPE ad_smtpadr,
      ls_history        TYPE /looply/history,
      ls_address        type BAPIADDR3,
      lt_return         type bapiret2_t.

SELECT-OPTIONS: s_uname FOR lt_usr01-bname.

START-OF-SELECTION.

  SELECT * FROM usr01 INTO TABLE lt_usr01 WHERE bname IN s_uname.

  LOOP AT lt_usr01 INTO ls_usr01.

CALL FUNCTION 'BAPI_USER_GET_DETAIL'
  EXPORTING
    username                = ls_usr01-bname
  IMPORTING
    ADDRESS                 = ls_address
  tables
    return                  = lt_return.

    CLEAR: ls_card_items, lt_card_items[], ls_card_data.

    CALL FUNCTION 'SAP_WAPI_CREATE_WORKLIST'
      EXPORTING
        user        = ls_usr01-bname
        language    = sy-langu
      IMPORTING
        return_code = lv_subrc
      TABLES
        worklist    = lt_worklist.

    CHECK lv_subrc EQ 0.
    lv_items = lines( lt_worklist ).
    CHECK lv_items GT 0.

    READ TABLE lt_worklist INTO ls_worklist INDEX 1.

* Prepare card data - header level

    ls_card_data-user = ls_usr01-bname.
    ls_card_data-name = ls_address-fullname.
    ls_card_data-email = ls_address-e_mail.
    ls_card_data-count = lv_items.

* Item level

    LOOP AT lt_worklist INTO ls_worklist.
      ls_card_items-workitem = ls_worklist-wi_id.
      shift ls_card_items-workitem LEFT DELETING LEADING '0'.

      concatenate: '<link to inbox app>'
      ls_worklist-wi_id
      '/TaskCollection(SAP__Origin='
      `'LOCAL_TGW',InstanceID=` `'`
      ls_worklist-wi_id `'`
      ')'
      into ls_card_items-wi_full.

      ls_card_items-wi_text  = ls_worklist-wi_text.
      APPEND ls_card_items TO lt_card_items.
    ENDLOOP.

    ls_card_data-items = lt_card_items.

* Call Looply.

    lv_data = /ui2/cl_json=>serialize( data = ls_card_data pretty_name = /ui2/cl_json=>pretty_mode-low_case ).

    SELECT SINGLE * FROM /looply/activity INTO ls_looply_trigger
      WHERE scenario = 'OO'
      AND   scenario_id = 'WF_INBOX'
      AND   scenario_version = '00'
      AND   step = '1'.

    lv_recipient = ls_card_data-email.
    lv_process_id = ls_card_data-user.

      CALL METHOD /looply/core=>trigger_wf
        EXPORTING
          im_recipient         = lv_recipient
          im_looply_wf         = ls_looply_trigger-looply_wf
          im_looply_wf_version = ls_looply_trigger-looply_wf_version
          im_scenario          = ls_looply_trigger-scenario
          im_scenario_id       = ls_looply_trigger-scenario_id
          im_scenario_version  = ls_looply_trigger-scenario_version
          im_step              = ls_looply_trigger-step
          im_process_id        = lv_process_id
          im_data              = lv_data
        IMPORTING
          ex_subrc             = lv_subrc.

   IF lv_subrc EQ 0.
        WRITE: / 'Trigger: ',  lv_process_id.
   else.
      CALL METHOD /looply/core=>resume_wf
        EXPORTING
          im_process_id       = lv_process_id
          im_data             = lv_data
          im_scenario         = 'OO'
          im_scenario_id      = 'WF_INBOX'
          im_scenario_version = '00'
          im_step             = '1'
        IMPORTING
          ex_subrc            = lv_subrc.
      WRITE: / 'Resume: ',  lv_process_id.
    ENDIF.
  ENDLOOP.

Summary

Now you are ready to test and roll out to specific groups of users.

Perhaps you could use a user parameter as an opt-in to receive Teams notifications – it’s probably not for everyone.

Since this is a one-way communication scenario, with only outbound data from SAP, the initial set up is really easy, with no authentication set up needed.

So you could be enjoying the benefits of Teams integration in days.

SAP Community - SAP ERP

REM Manufacturing

Updates on Conhecimento de Transporte Eletrônico and Manifesto Eletrônico de Documentos Fiscais

NF-e Technical Note 2019.001 v1.62: New Fields Added to Nota Fiscal

New fields added to the system

New table and fields for presumed credit information

New field for fiscal benefit code

Relevant SAP Notes for this legal requirement

NF-e Nota Técnica 2019.001 v1.62 novos campos adicionados à nota fiscal

Novos campos adicionados ao sistema

Nova tabela e campos para informações de crédito presumido

Novo campo para código de benefício fiscal

SAP Notes relevantes para esse requisito legal

NF-e Nota Técnica 2023.004 v1.10: novos campos adicionados à nota fiscal (Cloud)

Novos campos adicionados ao sistema

Grupo de Documentos de Importação

Grupo de ICMS

Mudanças em campos já existentes no sistema

How to add a new field to the VL06O,VL06I, VL06G… screens?

Linear programming in ABAP. Simplex method. Find optimised BOM

What is LP?

Example of optimization task. Creating an optimal BOM with necessary characteristics

How it can be solved in math way

SAP implementation for LP Simplex solver

Proof of concept. ZFI_SIMP_LP_DEMO

SAP Document and Reporting Compliance Brazil: Atualizações no CT-e MDF-e

Be an Expert with PLM System Integration Support Content!

SAP Document and Reporting Compliance Brazil: Dashboard do Usage Analytics

Join and innovate with the SAP Enterprise Support Advisory Council (ESAC) Program

What You Need to Know: Security and Compliance when Moving to a Cloud ERP Solution

What are the strategies to protect sensitive data?

How do you comply with regulations?

How can you minimize and mitigate cyber threats?

Where to learn more

Field Status Variant & Field Status Group

Retained Earnings Account

Jumpstart your cloud ERP journey with guided enablement in RISE with SAP Methodology

Unleash the power of Business AI across your Cloud ERP environment!

Trust in the data and AI recommendations

Welcome to Business AI

Creating an AI Business Strategy

SAP S/4HANA - Extracting User Email Addresses from Standard Tables

SAP Integration with SuccessFactors Through CPI: A Step-by-Step Handbook for Seamless Connectivity

Busting the Top 3 Myths about Cloud ERP Implementation

#1 Myth: ERP is for large enterprises.

#2 Myth: Cloud ERP is less secure than on-premises.

#3 Myth: ERP is a one-size-fits-all solution.

To learn more, please join us at the Secrets to Successful ERP Implementation webinar on May 22nd.

How to replicate your Fiori Inbox in Microsoft Teams

[1] Consider the trigger points.

[2] Build your Looply Workflow.

[3] Build your Adaptive Card in Looply

[4] Build the SAP trigger

Summary

To learn more, please join us at the Secrets to Successful ERP Implementation webinar on May 22nd.