Category Archives: Tips

Create and change SAP tables without coding or debugging

To create/change the content of a table (usually for test purposes), we typically use SE16 to write a report program or debug. But, with this tip, you can do it easily through a SAP standard technique without coding or debugging.Code:
1. Call transaction SE16N and enter the required table name to be edited(ex. KNA1).
2. type ‘&sap_edit’ in the command window and press enter key. The message ‘SAP editing function is activated’ will display.
3. Click on the execute online button (F8). Now the table will be in edit mode!

Unique Pricing condition

The pricing conecpt is built in SAP in such a way that there can only be one price in the sales document. So whenever there are multiple condition types (of condition class B Prices) in the sales document then by default system considers only the last condition type as active and the previous condition types will be made inactive. Since the conditions are inactive they would not add up to the netvalue of the document.

This does not apply for other condition types with condition class other than B (prices). Hence, all the discounts are considered in the net value of the document.

Configure Invoice Retention

Transaction Codes used – OBB8, OBB9

AR retentions: Contractually, the construction company and the owner define that a certain amount of the contract value is only paid after a certain timeframe (after a guarantee period). The retention amount can be calculated using SD conditions on the contract/sales order.

AR retention starts from the processes in L35: Contracting. When the contract is signed with the customer, the retention payment term is maintained on the contract to reflect this payment agreement.

When the billing point is reached, the project manager creates a billing document. The billing document can be configured to automatically transferred to finance to generate accounting document. The billing document can also be manually configured to check and release separately for additional authorization control

After the billing document is released to accounting, according to the defined retention term, the actual amount and due date of Accounts receivable is calculated and reflected on the account detail information. The accounting clerk can check this information.

The customer will pay the money according to retention. The accounting clerk entered the received money into the system to clear the relevant account receivable.

1 AR Retention

1.1 Check Customer Billing Document


In this activity, you check the billing document and release it.

In some cases, the billing document is automatically released. If the billing document has already been released, the Release to accounting steps below (steps 11 and 12) can be skipped.


The billing document was created in the L35 scenario, Contracting in section 2.6 Creating Billing Document.


1. Access the transaction choosing one of the following navigation options:

SAP R/3 menu

Logistics ®Sales and Distribution ® Billing ® Billing Documentà Change

Business Role

Project Manager

Transaction code


2. On the Display Order: Initial screen, in the Order field, choose F4 Help.

3. On the Search dialog box, on the Loading Agenda: Sales Doc. Grouped by PO. Number: Customer tab, enter the following data:

Field name


User action and values


Purchase Order Number

Test – Milestone*

Sold to Party


4. Choose Start Search. The system finds the Sales order number, 1 . Double-click it to enter the value in the Order field.

5. Choose Display Document Flow. On the Document Flow screen, select the Invoice 009xxxxxxx line item and choose Display document to display the document detail.

6. On the Invoice 9xxxxxxx (F2) Display: Overview of Billing Items screen, check the total amount of billing document, and make a note of the amount ___________.

7. From the menu, choose Goto à Header à Header.

8. On the Invoice 9xxxxxxx (F2) Display: Header screen, on the Header tab, in the Price data section, ensure that the value of the payment terms is RTN1.

9. Choose Back.

10. On the Invoice 9xxxxxxx (F2) Display: Overview of Billing Items screen, from the menu, choose Billing Document à Change.

11. On the Change Billing Document screen, choose Rel. to Accounting.

12. The system displays the message Document 9XXXXXXX has been saved.

13. Choose Exit twice.


An Accounting document is generated from the sales order billing document. This function can be automatically achieved when you create the billing document. Depending on the configuration, normally, the project manager usually checks the billing document first and then releases it to Accounting.

1.2 Display Customer’s Account Information


This activity displays the customer’s account information.


1. Access the transaction choosing one of the following navigation options:

SAP ECC 5.0 Menu

Accounting ® Financial Accounting ® Customers ® Account ® Display/Change Line Items

Business Role

Accounting Clerk

Transaction code


2. On the Customer Line Item Display screen, enter the following basic data:

Field name

User action and values






Line Item Selection:


Select Open items

Open at Key Date: Current Date


Select Normal Items

3. Choose Execute.

4. On the Customer Line Item Display screen, choose Change Layout.

5. From the Hidden Fields panel, choose the Net due Date and Payment term fields, then choose Show Selected Fields to transfer these fields from right panel to left panel.

6. Choose Copy.

7. One the Customer Line Item Display screen, find your created invoice document by looking up the document number.

There are two lines with this document number. Check the amount, payment due date and payment term. One line should have a 90% amount, a due date that is the current date, and a new payment term of 0001. Another line has a 10% retention amount, a due date of current date plus 1 year, and a payment term of BLCK.

8. Choose Cancel twice.


An invoice with Retention Payment Terms has been automatically split into two line items with different new payment terms.

Payment Term ZRT1 (due in 365 days)

Payment Term ZRT1 (due in 365 days)

Splitting the Payment into 90% and 10% (retention)

Splitting the Payment into 90% and 10% (retention)

Configure Downpayment

The following Customizing settings have to be made for down payment processing:

Settings for the billing plan – To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.

You need to implement the following activities in the billing plan for down payments:

Maintain deadline category – This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).

Maintain the deadline proposal – Use the down payments that are due for the proposed deadlines.

Maintaining a Pricing Procedure with the Condition Type AZWR:

In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.

Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.

Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.

Maintain the printing indicator – The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).

Maintaining the Billing Document – In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.

Copying control – Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.

Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.

Financial Accounting settings – A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:

Set reconciliation accounts (transaction OBXR) – For the `received down payments’ and `down payment requests’ from
the G/L accounts you have selected, you should assign the field status definition G031.

Maintain accounting configuration (transaction OBXB) – For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.

You must also carry out a G/L account number assignment for the tax account.

Maintain the posting key (transaction OB41) – For posting key 19, set the sales order as an optional field !!!

Maintain the field status definition (transaction OB14) – For field status variant 0001, field status group G031, set the
sales order as an optional field !!!

Assign the company code to the field status variants (transaction OBC5)

How to refrain users from changing some fields in T-code va02?

There are two ways to do this:
– Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
– You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.