Enhancing The Field Catalog of Condition Tables For Output Billing Documents

 The below steps helps us in adding a new custom field to the existing field catalog of a condition table on Output billing.

          1. Create a new structure (append structure) in KOMBZ – Customer groups. The newly added structure holds the new field.

                    

          2.  Enhance the structures KOMKBV3 (Header) and KOMPBV3 (Item) with the new field by adding an append structure.

                    

                    

          3. Now maintain V_T681F with the new field, this will add the new field to the condition table structure.

                    

              Click on new entries

                    

              

Add the new field.

          

                      

Save it.

4. Coding for filling the new field in RVCOMFZ1 form USEREXIT_KOMPBV3_FILL for the item field.

          5.  Coding for filling the new field in RVCOMFZZ form USEREXIT_KOMKBV3_FILL for the header field.

               

This will add the new field in the field catalog structure for access sequence, now we can create a condition table with this field and assign it to the Output type which will be triggered during the billing document creation.

To create a condition table use the transaction V/62.

Give the description and the field catalog will be shown as below with newly added fields.

Double clicking the required fields will move the fields to the selected fields list.

The technical view will help us in seeing the technical details of the selected fields.

The access sequence and output type are assigned to the billing application in NACE configuration and the data for the output type of the billing document is maintained using VV31.

Once this configuration is done, when a billing document is triggered with corresponding output type all the condition records are filled and we can see them from output messages tab on billing document using determination analysis.

The output will be seen in the analysis under the output message type with the condition table records.

Thank you.

Source: https://blogs.sap.com/2013/01/23/enhancing-the-condition-table-field-catalog-for-output-billing/

Enhancing The Field Catalog of Condition Tables For Output Billing Documents

 The below steps helps us in adding a new custom field to the existing field catalog of a condition table on Output billing.

          1. Create a new structure (append structure) in KOMBZ – Customer groups. The newly added structure holds the new field.

                    

          2.  Enhance the structures KOMKBV3 (Header) and KOMPBV3 (Item) with the new field by adding an append structure.

                    

                    

          3. Now maintain V_T681F with the new field, this will add the new field to the condition table structure.

                    

              Click on new entries

                    

              

Add the new field.

          

                      

Save it.

4. Coding for filling the new field in RVCOMFZ1 form USEREXIT_KOMPBV3_FILL for the item field.

          5.  Coding for filling the new field in RVCOMFZZ form USEREXIT_KOMKBV3_FILL for the header field.

               

This will add the new field in the field catalog structure for access sequence, now we can create a condition table with this field and assign it to the Output type which will be triggered during the billing document creation.

To create a condition table use the transaction V/62.

Give the description and the field catalog will be shown as below with newly added fields.

Double clicking the required fields will move the fields to the selected fields list.

The technical view will help us in seeing the technical details of the selected fields.

The access sequence and output type are assigned to the billing application in NACE configuration and the data for the output type of the billing document is maintained using VV31.

Once this configuration is done, when a billing document is triggered with corresponding output type all the condition records are filled and we can see them from output messages tab on billing document using determination analysis.

The output will be seen in the analysis under the output message type with the condition table records.

Thank you.

Source: https://blogs.sap.com/2013/01/23/enhancing-the-condition-table-field-catalog-for-output-billing/

How to Test BAPI Function Module in SAP?

 Introduction

As a SAP Consultant at some point of your career you will use BAPI. There is special way to test a BAPI whether it is really useful for you to call in your Program.

 

Solution

In our example we will be using BAPI_PO_CHANGE to change some fields in PO Line Item.

Now we will fill the Parameters and save it as a Test Data

Below is the Saved Test Data Entry

Now we go back to SE37 and follow the below path

We will put the following Function Modules.

Now we execute based on the saved Test data

After Executing we will hit Back Button and this will call the Commit Function Module

BAPI_TRANSACTION_COMMIT is called and we execute

Now executing is completed and the Database has commited.

 

Conclusion

We can use this Blog for both SAP ECC and SAP S/4HANA

 

Below is the video version

 

Also check how to Find BAPI

 

 Source: https://blogs.sap.com/2020/09/06/how-to-test-bapi-function-module-in-sap/

How to Remove Negative Entries from Customer Credit Master and SAP Table – S066 and S067

 Hello Everyone,

The following process will shed light on how to remove negative values shown in the Credit Management tables S066 and S067 and as well as shown in Customer Credit Master.

Problem Statement:

The issue is that negative values are shown in the Credit Management Tables – S066 and S067 – as well as in the Customer Credit Master. Due to this, the finance department of an organisation is not getting the correct credit exposure and details of open sale orders and deliveries of the customers. The system is allowing the creation of customer sale orders while the customer’s limit is over. Due to negative values, the system is not recognising the correct credit exposure.

Solution:

To overcome the above problem the following solution is as under to remove negative values from Table – S066 and S067 and also from Customer Credit Master.

 

Step-1:       Run the standard program RVKRED77 in T code-SE38 and place the customer number in the field of Credit account as per the below screenshot.

Step-2:         Go to Programme Menu—-> Click on Execute in Background as per the below screenshots.

Step-3:         After clicking on “Execute in Background” the following screen will be displayed. On this screen, write “LP01”  and click on the tick .

Step-4:         After clicking on the tick on the previous screen, the following screen will be displayed, also on this screen click on the tick icon.

Step-5:         After clicking on the tick on the above screen, the following screen will be displayed. In this screen, first, click on “Immediate”, then “Check” and finally click on the “Save” button.

Step-6:         After “Save” on the previous screen, execute T code-SM37 to check the status of the Credit re-org running programme. After executing T code-SM37, the following screen will be displayed, and click on the “Execute” button.

Step-7:         After executing the button on the above screen, If the status of the program/job shows “Active”, on the next screen then press the “Refresh” button on the upper left-hand corner of the screen. If the status shows “Finished”, it means the job has been completed successfully.

Step-8:         When the status is “Finished” as per the above screen, then execute program RVKRED88 in SE38, to fetch the details of open orders and delivery. Please put the customer number and press on the “Execute” button as per the below screenshot.

Step-9:         After executing the button as per the above screenshot, the detail of open orders and deliveries will be shown related to the customer.

To Conclude:

Once the above steps will be executed successfully the business will get the correct credit exposure of the customers to avoid any dispute in the future related to over-invoicing due to wrong credit exposure.

Suggestion:

To avoid any risk in Production system, instead to run both programs RVKRED77 & RVKRED88 directly in SE38, business can make Z T-codes to run this program in production system and give authorization to respective user for these T-codes to run these program.

Please follow Neeraj Jain for more content on issues & topics related to SAP Sales & Distribution and Material Management.

If any questions please click here

Thanks for your interest! Please share feedback, comments or suggestions below.

Best Regards,

Neeraj Jain

SAP Lead Consultant in HCL Technologies Limited

Source: https://blogs.sap.com/2022/09/06/how-to-remove-negative-entries-from-customer-credit-master-and-sap-table-s066-and-s067/

Debugging F110 (Automatic Payment)

 

Introduction

If you ever tried do debug the automatic payment program (F110), you had realized, it’s not that easy like at other SAP programs. The reason is, F110 creates a background job, where the payment items are processed. There are a handful of ways, to debug your payment job, in the following I will describe one of them. Let’s dive into it and learn, how to do it …

How to debug F110

Breakpoint for XDEBUG

First of all, to be able to activate debugging for F110, you need to change a variable at the payment program. Run SE38 and navigate to program F110MAIN and search for XDEBUG.

set breakpoint the change XDEBUG variable

Create a breakpoint to stop at this program line.

Job Scheduling

Next step, you have to schedule your payment job into the future. This is necessary, to be able to run the background job in debugging mode.

schedule automatic payment

 

Background Job Debugging

Once, the background job is scheduled, run SM37, select your created F110 job and run command JDBG into the command-field. The same function can be selected under menu Extras / Debug Job.

select background job and run job debugging

Activate Debugging

The job will start immediately. Continue with F8 and the debugger will stop at your breakpoint created before.

Now you have to change the variable XDEBUG to “X”.

Debug

Now you can run the program to your code of interest, which you want to debug.

Final words

You can not debug F110 as easy as other SAP programs, but with a little bit of extra work, you get it done without any problems.

If you have any questions, feel free to use the comment section below

Source: https://blogs.sap.com/2020/09/23/debugging-f110-automatic-payment/

SAP TM Integration with LBN for Freight tendering

 Shippers, Manufacturers use this business process to send freight requests for quotation (freight RFQs) to carriers. Carriers can accept or decline these freight RFQs and change data such as the price when they return the freight quotations. Shipper can then automatically accept the tendering and send the freight order back to the awarded carrier. You can define a timeout in the system so that the system either tenders the freight order to another carrier or switches from one tendering type to the next. The tendering process results in one carrier being selected to execute the freight order.

Typical Tendering Process between TM and LBN is explained using below flow chart:

Note:

• This integration is between TM and LBN Freight Collaboration
• SAP standard Web Service communication is used via SOAMANAGER configuration for integration between TM <-> LBN.

This process runs as follows:

1. Start tendering from TM Freight order

You start the tendering process. The process can be initiated by selecting an existing tendering profile. The tendering steps can also be created manually and stored as a tendering template. The process can involve the following:

• Definition of price limits and time limits
• Assignment of visibility settings (determines whether a carrier is allowed to change prices and dates)

• Perform peer-to-peer tendering

The system sends the freight RFQs or freight orders one after the other to the specified carriers.

• Perform broadcast tendering

The system sends the freight RFQs to all carriers simultaneously.

2. Create RFQ from TM system– Send out freight requests for quotation (freight RFQs) to one or more carriers, according to a tendering plan.
   • You can send the freight RFQs manually
   • You can enable the system to send freight RFQ’s out automatically.
   • You can also use a direct tendering process to send a road freight order (road FO) directly to a specified carrier without creating a freight RFQ. Carriers can confirm or reject the road FOs. Unlike the freight RFQ process, the system generally awards a carrier if he or she does not reject the road FO within a given time limit.

Direct tendering can be created and started manually by the user, or automatically by the system.

3. Carrier Acceptance or Rejection of a Freight Request for Quotation via LBN
   • Quotation that was created in Step2 must have received into LBN.
   • A carrier must respond to the sold-to party within the time limit given in the freight request for quotation (freight RFQ). The carrier must accept or reject the freight RFQ before the response time ends.
   • Open the application ‘Freight Requests for Quotation’ in Carrier tenant LBN portal
   • Carrier can see Tendering Quotation received into LBN
   • Carrier can Accept / Reject / Accept with changes

 

4. Evaluation of Freight Quotations in TM system
   • If the Carrier response is Accept, Response code is ‘Accepted and Evaluation pending’ against the Tendering Quotation Request in TM system.
   • If the carrier response is Reject, then RFQ status is updated as rejected and a new RFQ can be initiated again.
   • Shipper can evaluate freight quotations immediately after carrier has responded them.
   • Tendering manager Evaluates FQs to detect that the maximum response time for a RFQ time is over.
   • Additional evaluation criteria:
     • Lowest price
     • Carrier who commits to stop date
     • Fastest carrier
   • To evaluate the RFQ process automatically in TM system, program /SCMTMS/TEND_CONT_PROCESS can run in foreground / background as a batch job.

5. Award a freight quotation in TM system
   • Immediately after Freight quotation is awarded to a carrier, following information is updated in freight order.
   • Selected carrier
   • Submitted price
   • Charge hierarchy
   • Confirmed stop dates and times

 

The system sends the freight order as a transportation request to the carrier. The carrier can receive the transportation request on the mobile device using SAP Transport Tendering.

In this step, Tendering is Awarded to carrier and sent for confirmation to Carrier.

After awarding to carrier, Status of RFQ is updated to Awarded in TM Freight order.

6. Carrier confirmation from LBN portal
   • After Shipper awarded it to carrier, Freight order is received in to LBN for confirmation from Carrier.
   • Carrier login to LBN portal in respective carrier tenant -> Open the application ‘Freight Orders for Confirmation’ to see if any freight orders waiting for confirmation.
   • Carrier confirm the shipment, and then shipment execution can began as per the requested dates.

Pre-requisites:

• Customizing settings for tendering
• A tendering plan
• Define freight order types that are relevant for subcontracting.
• Carrier BP in TM
• LBN Carrier tenants
• LBN Shipper tenant
• SAP Standard Web Service SOAMANAGER configuration between TM <-> LBN

Source: https://blogs.sap.com/2022/09/06/sap-tm-integration-with-lbn-for-freight-tendering/