business process procedures - sap service …sapidp/... · web viewthis procedure is known as...

EHP7 for SAP ERP 6.0

July 2014

English

Subsequent Settlement (725)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Subsequent Settlement (725): BPD

Copyright

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE of 2

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE Page 2 of 2


Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites.......................................................................................................................... 5

2.1 Checking User Parameters.............................................................................................5

2.2 Business Conditions........................................................................................................6

2.3 Overview the Related Master Data..................................................................................6

2.4 Roles............................................................................................................................... 6

3 Process Overview Table.........................................................................................................7

4 Business Process................................................................................................................... 9

4.1 Displaying Arrangement Status.......................................................................................9

4.2 Creating Arrangements.................................................................................................10

4.3 Creating Purchase Order...............................................................................................13

4.4 Executing Goods Receipt..............................................................................................14

4.5 Executing Invoice Verification........................................................................................15

4.5.1 Entering Invoice.....................................................................................................16

4.6 Checking Update of Business Volume..........................................................................17

4.7 Displaying Detailed Statement......................................................................................18

4.8 Generating Business Volume with ECATT (for interim settlement)...............................19

4.8.1 Optional: Interim Settlement...................................................................................20

4.9 Generating Business Volume with ECATT (for partial settlement)................................21

4.9.1 Executing Partial Settlement..................................................................................22

4.10 Executing Business Volume Comparison..................................................................24

4.11 Executing Final Settlement........................................................................................25



Subsequent Settlement

1 PurposeBuyers and representatives of vendors normally negotiate prices at least once a year.

Some of the conditions agreed with the vendor are not settled in the goods invoice but are settled instead at a later date. This procedure is known as "subsequent settlement". This involves conditions that depend on the goods procured, such as annual quantity discounts, incremental and account end-of-period rebates, and conditions that are independent of the goods procured, such as promotion rebates, disposal rebates, and listing money.

The subsequent conditions negotiated with the vendor are entered in the system, whereby the conditions that are valid within the same period and must be settled at the same time are grouped together to form rebate arrangements. The starting point for a rebate arrangement can be backdated here.

Within the validity period for each rebate arrangement, the sales for all conditions that depend on the goods procured are updated on the basis of the verified vendor invoice. If the starting point for the rebate arrangement is in the past, the past sales can be assigned using a subsequent statistics structure. When the goods are received, provisions can be created for the expected revenues. The value of the goods received is then reduced by the provision amount or percentage. In this way, the stock no longer needs to be adjusted on a value basis after final settlement has been carried out, provided that the provision matches the amount that has actually been settled.

Interim or partial settlements can be used if part of the rebate is to be posted to a rebate arrangement before the rebate arrangement expires.

Partial settlements can be carried out by defining period-specific conditions. Interim settlements can be used for rebate arrangements that must be settled either once or periodically. With interim settlements, you have to enter the end date of the current period as the settlement date. In this case, the rebate arrangement conditions that would otherwise not yet be due during the settlement run (because either the end date of the rebate arrangement or next end date of a period have not yet been reached) are also settled. The conditions remain active and are taken into account in the next partial or final settlement.

If you and the vendor have agreed upon a sales reconciliation, the relevant sales data updated at your company and at the vendor's company is compared before the final settlement. If any discrepancies are identified, you have to decide upon an agreed value. This sales data is then used as a basis for final settlement. In the final settlement, the interim and partial settlements that have already been carried out are offset against each other.

Debit-side settlement (the vendor is debited) or credit-side settlement (the vendor sends a credit memo) is possible. In both cases, the system generates a financial accounting document.

2 PrerequisitesIf you start Subsequent Settlement for the first time, make sure that only your own arrangements are active for a vendor (for example, PCS-V411). Detail description: see section4.1

2.1 Checking User ParametersUseIn this step, check the user parameters and the default settings.

Procedure1. On the toolbar, choose the Customize Local Layout (Alt+F12) button, and select Options.



2. In the Options dialog box, choose the Expert tab.

3. Make sure the Show Keys in All Dropdown Lists field is selected.

4. Choose OK.

Only for SAP Logon 720

1. Choose Interaction Design in the left panel.

2. Choose Visualization & Interaction in the left panel.

3. Choose Show keys within dropdown lists and Sort by keys within dropdown lists for most efficient keyboard input.

5. Access the activity using one of the following navigation options:

Transaction code SU3

Toolbar Menu System User Profile Own Data

6. On the Defaults tab, make the following entries:

Field name Description User actions and values Comment

Start menu W10T Fixed Values

Decimal Notation 1.234.567,89 Fixed Values

Date Format 1 DD.MM.YYYY Fixed Values

7. Save the entries.

8. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).

Or

Choose Exit (Shift+F3) to close the transaction.

2.2 Business ConditionsThe business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scope items.

For this scope item there are no business conditions.

2.3 Overview the Related Master Data

ProcedureFor the execution of the scope item, use the master data matching your installation of the pre-configured system. You can find corresponding identifiers in the following table:

Fashion Hard goods Food

ArticLe PCS-01-ART141 PCS-01-ART413 PCS-01-ART333

Vendor PCS-V141 PCS-V411 PCS-V331

Company Code 1000 1000 1000

Purchasing organization

1000 1000 1000

Purchasing Group 100 100 100

2.4 Roles© SAP SE Page 2 of 2


UseThe following roles must have already been installed to test this scope item in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scope item. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scope item.

Technical name Business role Process steps

SAP_NBPR_SUBSETTLEMENT_RT_S Retail Buyer Subsequent Settlement

Assignment of this role is necessary for basic functionality.

SAP_NBPR_NONSEASBUYER_RT_SRetail Non-Seasonal Purchaser

Assignment of this role is necessary for basic functionality.

3 Process Overview TableProcess Step External

Process Reference

Business Condition

Business Role

Transaction Code

Expected Results

Display Arrangement Status

Retail Buyer (Subsequent Settlement)

MEB3

Create Arrangements


MEB1 Rebates xxx created. Note the number of the arrangement.

Create Purchase Order

Retail Non-Seasonal Purchaser

ME21N Standard PO created under the number xxx. Write down the number of the purchase order.

Post Goods Receipt


MB01 Document 5000xxx is posted

Execute Invoice Verification


ME81 Net order value is displayed (EUR). Write down the amount.

Enter Invoice Retail MIRO Document



Process Step External Process Reference

Business Condition

Business Role

Transaction Code

Expected Results

Buyer (Subsequent Settlement)

number.5105xxx is created.

Check Update of Business Volume


MEB3

Display Detailed Statement


MEB8

Generate Business Volume with ECATT (for interim settlement)

SECATT

Optional: Interim Settlement


MEB4

Generate Business Volume with ECATT (for partial settlement)

SECATT

Execute Partial Settlement


MEB4

Execute Business Volume Comparison


MEU2 Business volume comparison/ agreement changes effected.

Perform Final Settlement

Retail Buyer (Subsequent Settlement

MEB4



Process Step External Process Reference

Business Condition

Business Role

Transaction Code

Expected Results

)

4 Business Process

4.1 Displaying Arrangement StatusUseYou can save arrangements with your vendors in the system. These can involve one-time or periodically settled conditions.

A condition is an individual agreement within an arrangement. They can be valid for goods (for example, for the vendor’s entire assortment, for a partial assortment, a merchandise category or an article) and for organizational units (for example, stores/DC’s that are assigned to a purchasing organization). If a condition is valid for multiple articles that do not belong to the same vendor sub-range, the articles can be combined in a settlement group.

The valid condition types and their organizational levels (the key-fields) are created in customizing. See the Customizing Guide for Settlement for details.

In our example, you create a bonus for the entire assortment of a vendor. The bonus is calculated in percent from the purchase order value.

In practice, the arrangements created for vendors last an entire year or even longer and are then simply extended.

Arrangements involve master data. If more than one person applies the example in this documentation on the same SAP client with the same data, multiple arrangements for a vendor with the same validity period is created. These are all active! If you are acting out this documentation for the first time, make sure that no other arrangements are active for your vendors (for example, PCS-V411). An arrangement is active when it has not been finally settled (status D). Do not forget that during posting of goods receipt in accounting, the accruals for active arrangements are created.

The following describes how to find arrangements that have not been finally settled and then execute final settlement for them.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Rebate Arrangement Display

Transaction code MEB3

Option 2: SAP Netweaver Business Client (SAP NWBC) via Business Role

Business role Retail Buyer Subsequent Settlement

(SAP_NBPR_SUBSETTLEMENT_RT_S )

Business role menu Subsequent Settlement Subsequent Settlement Display Agreement

2. Choose F4. The Restrict Value Range screen appears.

3. On the Arrangements by condition granter tab, enter the following:



Field name Description User action and values Comment

Condition granter PCS-V141 (Fashion) PCS-V411 (Hard goods) PCS-V331 (Food)

4. Choose Start Search (Enter).

If no arrangement exists for the vendor, you get the system message: No values for this selection. If an arrangement exists, write down the number of the arrangement(s) which are not in agreement status D (= no final settlement of agreement already carried out) and continue with section: 4.10 and 4.11.

5. Choose Close.


Or


4.2 Creating ArrangementsUseThe validity period of an arrangement is freely selectable, unless an arrangement calendar has been stored in customizing. In our example, a yearly arrangement calendar has been saved. The arrangement runs from today until the end of the current year.

If you would like to settle a condition periodically, you must create a settlement calendar. The calendar sets the validity period of the period-specific condition as well as the time for the settlement. In our example, monthly settlement is done.

Each condition represents a rebate. This consists of an amount (for example, percentage, fixed amount) and a unit (%, EUR). This means that the amount can refer to a value, a quantity, a weight or a percentage. A condition can be scaled or un-scaled. An un-scaled rebate is constant. If you create a scale, the first level of the scale must be reached or the system calculates a rebate of zero.

If the arrangement has a settlement calendar (as in our example), period-specific conditions are automatically created. These match the main condition as proposed values, but can be changed. In addition, amounts for the accruals are created; these are also taken from the main condition. The amounts of the accruals can also be changed; for example, the accrual amount can be set more conservatively than the condition if you are not sure if you will fulfill the condition. Naturally, it is best when the accrual and the condition correspond to each other, since the accrual is considered in the moving average price in the article master and in the accounting.

To see how the system works and how it determines the condition records, different condition records are selected for the main condition, scale, period-specific condition and accrual in the arrangement that you will create.

The bonus consists of a main condition that calls for a 13% rebate. In the arrangement, a scale is integrated which says that we receive this 13% above a business volume of 10.000 EUR. If we reach a business volume of 30.000 EUR, we will get a rebate of 15%. The system creates the appropriate period-specific condition and the accruals at 13%. In the first month, however, only a bonus of 12% is granted. The first period-specific condition is changed to 12%. We set the accrual amount for the first month at 10%.





SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Rebate Arrangement Create



Business role Retail Buyer Subsequent Settlement (SAP_NBPR_SUBSETTLEMENT_RT_S)

Business role menu Subsequent SettlementSubsequent SettlementCreate Agreement

2. On the Create Agreement screen, make the following entries:


Agreement type 1000 Rebates

3. Choose Enter.

You may receive message AJ logistics calendar not maintained. If so, within customizing, maintain arrangement logistics calendars valid to year.

4. In the Organizational Data message dialog box, make the following entries:


Purch. Organization 1000

Purchasing group 101

5. Choose Copy.

6. On the Create Rebates: Overview Agreement screen, make the following entries.


Condition granter PCS-V141 (Fashion)PCS-V411 (Hard goods)PCS-V331 (Food)

Currency EUR

Validity period Date (today)

To Date (End of the year)

Comp. BV necessary:Final settl.

Select

7. Choose Conditions(For NWBC , MoreGotoConditions)

8. If you get the system message: Bus. vol. Comparison not defined for partial settlement of arrangement, ignore it.

9. In the dialog box, choose Vendor and select Choose (Enter).

10. On the Create Rebates: Overview Rebates (A001) screen, make the following entries.


Vendor PCS-V141 (Fashion)PCS-V411 (Hard



goods)PCS-V331 (Food)

Amount 13 (%)

11. Choose Enter.

12. Confirm the message: Period-specific conditions successfully created by choosing Enter.

13. Select the first row and choose Details.

14. In the Artl f. settl. field, make the following entries and choose Enter:


Article f.settl. PCS-01-ART141

PCS-01-ART413

PCS-01-ART333

Fashion

Hard Goods

Food

15. Choose Scales (F2).

16. On the Create Rebates: Scales Rebates (A001) screen, make the following entries.


Scale value 300000

ScCur EUR

Amount 13

Enter in next row:

Scale value 900000

Amount 15

17. Choose Enter.

18. Choose Back.

19. Select the first row, and then choose Period-Specific Conditions (Shift+F7).

20. On the next screen, make the following entries.


Amount 12.000- (%) Change the period-specific conditions only for the first month

Accruals 10.000- (%) The other month must be 13 %.

21. Choose Enter.

22. Choose Save.

23. The message: Rebates … created, appears. Note the number of the arrangement _______


Or




4.3 Creating Purchase OrderUseThe purchase order is the basis for the business volume update. In the order, pricing is conducted. This is based on the calculation conducted in the article. As a part of pricing, the system checks whether there is a condition that has been agreed with this vendor for this article. The conditions relevant for accruals, that is, the conditions that are settled subsequently, are considered. The value of the accrued business volume is shown during the purchase order creation.

If you order 250 pieces for example, you can comprehend the amounts in the documentation.

Procedure1. Access the transaction using one of the following navigation options:


SAP ECC menu Logistics Retailing Purchasing Purchase Order Purchase Order Create Vendor Known

Transaction code ME21N


Business role Retail Non-Seasonal Purchaser (SAP_NBPR_NONSEASBUYER_RT_S)

Business role menu Purchasing Non-Seasonal Purchase Management Purchase Orders Create Purchase Order

2. On the Create Purchase Order screen, make the following entries.


Order type (to the right of basket)

NB Standard PO

Vendor PCS-V141 (Fashion)

PCS-V411 (Hard goods)

PCS-V331 (Food)

Doc. date <Date> (Displayed)

3. Expand the Header.

4. Confirm the message: Enter Purchasing Org., with Enter.

5. On the Org. Data tab, make the following entries:


Purch. organization 1000

Purchasing Group 101

Company Code 1000

6. Expand Item Overview.

7. Make the following entries:




Article PCS-01-ART141

PCS-01-ART413

PCS-01-ART333

Fashion

Hard goods

Food

PO quantity 250

Order Unit (Oun) PC

Delivery date Current date + any time in future (must be a working day)

Site VZ01

8. Choose Enter.

If you use a generic Fashion article, maintain the variant quantities (divide the order amount of 250 PC in the matrix)

9. On the Invoice tab, for the each item of the Purchase order,enter the following:


Tax Code V2

10. Choose Save.

11. You get the system message: Standard PO created under the number…..

12. Make a note of the purchase order number __________________.

13. Choose No to cancel the printing window.


Or


4.4 Executing Goods ReceiptUseWhen, according to the condition type, an accrual for the expected business volume is to be made, it is posted at the time of goods receipt and the moving average price adjusted accordingly in the article master.



SAP ECC menu Logistics Retailing Merchandise Logistics Inventory Management Goods Movement Goods Receipt For Purchase Order PO Number Known

Transaction code MB01


Business role Retail Buyer (Subsequent Settlement)



(SAP_NBPR_SUBSETTLEMENT_RT_S)

Business role menu PurchasingNon-Seasonal Purchase ManagementPurchase Orders Post Goods Receipt for PO

2. On the Goods Receipts for Purchase Order: Initial Screen, make the following entries.


Movement type 101

Purchase order PO number of

Site VZ01

Storage Location 1001

3. Choose Enter.

4. Choose Save (Post).

For generic article, choose Post twice.

5. Confirm the warning message: Enter delivery note for evaluated receipt settlement, with Enter.

6. Confirm the message with Enter if it is necessary.

7. You get the system message: Document 50000xxxxx posted.

8. Write down the document number ___________.

4.5 Executing Invoice VerificationProcedure1. Access the transaction using one of the following navigation options:


SAP ECC menu Logistics Retailing Purchasing Purchase Order Purchase Order Analyses Analysis of Order Values

Transaction code ME81


Business role Retail Buyer Subsequent

Settlement


Business role menu Subsequent Settlement Subsequent Settlement Analysis of Order Values

2. On the Analysis of Purchase Order Values screen, make/check the following entries.


Currency for Analysis EUR

Purchasing organization 1000



Purchasing Document PO number of

Interactive Analysis ‘x’ (other fields without entries)

3. Chose Execute twice.

4. Net order value is displayed (EUR).

5. Write down the net order value ____________.


Or


4.5.1 Entering Invoice

UseWhen a vendor invoice is received, a check against the purchase order and the delivery (goods receipt) is made. If the vendor invoice is correct, the invoice data (business volume, sales) is updated.



SAP ECC menu Logistics Retailing Purchasing Logistics Invoice Verification Document Entry Enter Invoice

Transaction code MIRO


Business role Retail Buyer Subsequent Settlement(SAP_NBPR_SUBSETTLEMENT_RT_S)

Business role menu Subsequent Settlement Subsequent SettlementEnter Incoming Invoice

2. In the message dialog box, enter 1000 for the Company Code field.

3. Choose Enter.

4. On the Basic data tab, make the following entries:


Invoice Date current date

Posting Date current date

Amount See the step 4.5 Net order value+tax value

Currency EUR

Tax code V1

Calculate Tax 'x'

‘PO reference’ tab

Selection Enter Purchase Order see



step

‘Payment’ tab

BaselineDt current date

5. Choose Post.

6. Document number.5105xxxcreated (Blocked for payment).

The document will be posted and the corresponding account movements will take place. However, the invoice must be released in a separate step before payment can be made (transaction MRBR).You can check the blocking reasons (in this case R Invoice Verification) via transaction MIR4/Payment tab.


Or


4.6 Checking Update of Business VolumeUseThe business volume data is automatically updated for the goods and business unit in question. This update can be triggered by the purchase order, the goods receipt, or the invoice verification.



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Rebate Arrangement Display



Business role Retail Buyer Subsequent Settlement (SAP_NBPR_SUBSETTLEMENT_RT_S)

Business role menu Subsequent Settlement Subsequent SettlementDisplay Agreement

2. On the Display Agreement screen, make the following entries:Field name Description User action and values Comment

Agreement see step 4.2

3. Choose Enter.

4. Choose (NWBC: More…)SettlementDisplay Business Volume, from the menu bar.

5. In the message dialog box: Business Volume Rebate Agreement XX, select the List period data.

6. Choose Continue (Enter).

7. Choose Cancel




Or


4.7 Displaying Detailed StatementUseIn this evaluation, you see the purchase order, the goods receipt, and the invoice verification documents. In addition, you can go to the corresponding accounting document to see the accruals. The system has determined the condition record of 10% for the accruals of the first month. If you observe the accounting documents throughout the document update process, you will see the postings listed below.



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements List Displays Detailed Statement





Business role menu Subsequent SettlementSubsequent SettlementDet. Statement, Vendor Rebate Arrs.

2. On the Detailed Statement: Vendor Busn. Vols.: Reb,Arrangements,Purchasing screen, make the following entries.


Rebate arrangement See step 4.2

Arrangement type 1000

3. Choose Execute.

4. Double-click on the purchase order number 45000xxx. (Purchase order is displayed in detail).

5. Choose Back.

6. Choose (NWBC: More…)Goto Disp. doc. update from the menu bar. (Article document is displayed in detail).

7. Choose Back.

8. Place the cursor on the purchase order number 45000xxx, and then choose PO history on the title bar.

9. Choose invoice 51056xxxxx (Invoice is displayed).

10. Choose Follow-on Documents (payment advice is displayed with the designated account assignments).

11. Choose Back three times.



12. Choose (NWBC: More…)Goto Display condition record from the menu bar, Rebate scale is displayed, View it and then choose Back.

13. Choose Back twice.


Or


4.8 Generating Business Volume with ECATT (for interim settlement)

UseThe ECATT is a tool for testing and executing business transactions in the SAP ERP system. It automatically executes the same steps (transactions in the system) that you have done in the sections 4.3 Create Purchase Order, 4.4 Execute Goods Receipt and 4.5 Execute Invoice Verification. If you execute the ECATT in the foreground, you will see that the same fields are filled in automatically. However, a background execution is easier and faster.

This ECATT is set so that you will order 250 pieces. Instead of the ECATT, you can execute the purchase order, goods receipt, and invoice verification steps again.

Procedure1. Access the transaction using the following navigation option:

SAP ECC menu Tools ABAP Workbench Test Test Workbench Test Tools Extended eCATT

Transaction code SECATT

2. On the Extended Computer Aided Test Tool: Initial Screen,, make the following entries:


Test Configuration Z_DE_CREATE_BUSINESS_VOLUME

3. Choose Execute.

4. On the Start Options - Test Configuration: Z_DE_CREATE_BUSINESS_VOLUME screen, make the following entries:


Error Behavior ‘S No Termination, Continue with Next Script Command’

5. Choose the Variants tab.

6. In the Selection of Internal Variants subscreen, the following variant choice is displayed:


Selection 100001 Fashion

300001 Food

400001 Hardgoods

7. In the Execute column, uncheck the variants for which you do not want to execute the ECATT (for example, for Fashion ECATT, you need to uncheck Food and Hard Goods).



8. Choose the UI Control tab.

9. Make the following entry:


Start Mode for Command TCD

‚N Process in Background, Synchronous Local’

10. Choose Execute.


Or


4.8.1 Optional: Interim Settlement

UseInterim settlement should never be used systematically, but only in exceptional cases (that is, danger that the vendor will not be able to meet commitments). Partial settlement is used to settle arrangements before their validity period is over. Each partial settlement corresponds to a period-specific condition record, for which the business volume data and rebate income are updated. Each condition record is settled one time only, whereupon the data is frozen. This ensures transparency in case of errors.

Interim settlement, on the other hand, creates rows of dominoes of settlements based on each other. Extreme example: daily settlement with 230 settlements all based on the one before. An error is apparent in settlement 230, but settlements 1 to 229 can no longer be restored and even the data of settlement 230 has changed due to continual updates of business volume. Summary: Interim settlement is possible, but it must be understood that in case of error, error analysis and handling is not possible on the part of SAP. Of course, the data set itself can be corrected. See also note 167284.

At the end of the validity period of an arrangement, or at the end of an agreed period for periodic settlement (agreed and set in the settlement calendar), the system calculates the rebate income for the conditions that are due and creates the settlement documents.

Interim settlement can be conducted for arrangements that are to be settled once as well as for those that are to be settled periodically. With interim settlement, the condition records keep their active status. Business volume continues to be updated, and these will be settled again (with partial settlement or final settlement). The previously settled rebate income is considered in this calculation.

In our example, you want to settle the business volume in the middle of the month, although the agreement is to be settled at the end of the month according to the settlement calendar. In the report, you enter the last day of the month as the settlement date but set the indicator interim settlement in place of the final settlement indicator.

Therefore, conditions that have not yet been settled can always be settled in the interim.

The successfully created settlement is automatically posted in accounting according to its type (debit or credit). In our example it is on the credit side, that is, an invoice is created for the vendor, which corresponds to a credit memo to our advantage in the vendor account.

For the interim settlement, the system withdraws the accrual amounts posted during goods receipt for the first month (10% of 30.000 EUR order value). At the same time, it determines the rebate for the first month based on the period-specific condition (12% of 30.000 EUR order value) and posts this.

The balance in the account Z0000000 TECHNICAL CORRESPONDENCE is 600 EUR. This shows the difference between accruals and settled conditions. In our example, the calculation is



2% difference (accrual was 10%, period-specific condition was 12%) based on 30.000 EUR order value = 600 EUR.



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Rebate Arrangement Create Settlement Document Via Report





Business role menu Subsequent SettlementSubsequent Settlement Settlement re Vendor Rebate Arrs.

2. On the “Settlement: Vendor Rebate Arrangement, Purchasing ” screen, make the following entries:


Rebate arrangements

Rebate arrangement see step 4.2.

Settlement date End-date of the first month of the arrangement

Control data for settlement document

Billing date (posting date) Date

Control data: settlement run

Settlement: Execute select

Condition records

Perform interim sett. accounting

select Do not perform settlement accounting! (final settlement!)

3. Choose Execute.

4. Set cursor on the words Interim settlement and choose Sett.Doc.

5. Choose Accounting.


Or


4.9 Generating Business Volume with ECATT (for partial settlement)

Use



Instead of the ECATT, you can execute the purchase order, goods receipt and invoice verification steps again with an order quantity of 250 pieces (that is, 1800 x 250 PC. = 15000 EUR).

Procedure1. Access the transaction using the following navigation option:

SAP ECC menu Tools ABAP Workbench Test Test Workbench Test Tools Extended ECATT

Transaction code SECATT

2. On the Extended Computer Aided Test Tool: Initial screen, make the following entries.


Test Configuration Z_DE_CREATE_BUSINESS_VOLUME

3. Choose Execute.

4. On the Start Options - Test Configuratn: Z_DE_CREATE_BUSINESS_VOLUME screen, make the following entries:


Error Behavior ‘S No Termination, Continue with Next Script Command’

5. Choose the Variants tab.

6. In Selection of Internal Variants subscreen, the following variant choice is displayed:


Selection 100001 Fashion

300001 Food

400001 Hardgoods

7. In the Execute column, uncheck the variants for which you do not want to execute the ECATT (for example, only ECATT for Fashion: you need to uncheck Food and Hard Goods).

8. Choose the UI Control tab.

9. Make the following entry:


Start Mode for Command TCD

‚N Process in Background, Synchronous Local’

10. Choose Execute.


Or


4.9.1 Executing Partial Settlement

UseWith a partial settlement, only the sales volume of the respective validity period is settled. In this way, expected values can be maintained.



Example: Settlement based on the sales of a validity period, for example, July 2011. The revenue can be interpreted as an expected value, which means, for example, for the final settlement: above EUR 1 million 1%, above EUR 2 million 2%, above 3 million 3 %. Sales volume of 2.5 Million is expected for the year. 2% is entered in the period.

For the partial settlement of the first period of the arrangement, the system must observe the interim settlement conducted previously as well as the new accrual from the second ECATT run. First, the accrual from the second ECATT run is revoked. In addition, the new rebate is determined based on the period-specific condition of 12% and the business volume (12% off 15,000 EUR order value). The previous rebate from the interim settlement is withdrawn. But because the vendor has already been debited for this, only the rebate of the additional income in the second ECATT run is charged to the vendor account.

The balance of the account Z0000000 TECHNICAL CORRESPONDENCE has grown to 300 EUR. The balance is the difference between accrual and settled condition. This calculation is 2% difference (accrual 10% and period-specific condition 12%) of 15000 EUR order value = 300 EUR.

The update is done for each condition that is valid. Once a condition is settled (partial or final settlement), no business volume update is done. The status is C (settlement created).



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Rebate Arrangement Create Settlement Document Via Report





Business role menu Subsequent SettlementSubsequent Settlement Settlement re Vendor Rebate Arrs.

2. On the Settlement: Vendor Rebate Arrangement, Purchasing screen, make the following entries.


Rebate arrangements

Rebate arrangement see step 4.2: Create Arrangements

Settlement date End-date of the first month of the arrangement





Condition records

Perform interim sett. accounting

select Do not perform settlement accounting! (final settlement!)



3. Choose Execute.

4. Set cursor on the word Interim settlement and choose Sett.Doc.

5. The Choose settlement document screen appears. Choose the last document and choose Enter.

6. Choose accounting to check the document.


Or


4.10 Executing Business Volume ComparisonUseA business volume comparison is optional, but in our scope item it was marked as necessary during the creation of the agreement (compare to 4.2: Create Arrangements).

The system constantly updates the volume of business with vendor. However, your values can differ from those of the vendor (because of different limitations, for example). The business volume comparison is designed to reach agreement with the vendor before final settlement is done and thereby avoid corrections after the final settlement.

So if the results of your business volume update vary from those of the vendor, the business volume comparison is executed and the resulting agreed value is the basis for the final settlement.



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor Rebate Arrangements Business Volume Comparison Execute

Transaction code MEU2


Business role Retail Buyer Subsequent Settlement(SAP_NBPR_SUBSETTLEMENT_RT_S)

Business role menu Subsequent Settlement Subsequent SettlementPerform Busn. Volume Comp.: Rebate

2. On the Perform Comparison of Business Volumes screen, make the following entries.


Agreement See step 4.2

3. Choose Enter.

4. Select the first row and choose Activate Comparison.

5. Confirm the system message: Business volume comparison for the condition was activated, with Enter.

6. Then make the following entries.



Field name Description User action and values

Comment

Scale basis 1500000 (For example)

Displayed; the amount depends on the agreement

Condition basis 1500000 (For example)

Displayed; the amount depends on the agreement

7. Choose Save.

8. You get the system message: Business volume comparison/ agreement changes effected.


Or


4.11 Executing Final SettlementUseBased on the system date, the system can recognize if a partial settlement or a final settlement is to be executed. On 12/31/2011, a final settlement is done rather than a partial settlement.

Final settlement must be conducted. This is important in case other users apply this documentation on the same system with the same data (vendor, article). Otherwise, multiple arrangements are active and during goods receipt the system generates accruals for all active agreements. The resulting posting records would be difficult to follow for the agreement of a particular tester.

During final settlement, the system must observe the settlements that have already been done. The status of the arrangement is set to D (final settlement done). The system withdraws the rebate income already posted to account Z0000000 during the last partial settlement. To determine the new rebate income, the condition record of the scale is now used. Since the agreed business volume has reached the amount set forth in the scale, the rebate is 15% of 50000EUR. The difference between the two amounts of rebate income is charged to the vendor account.

The balance of the account Z0000000 (TECHNICAL CORRESPONDENCE) shows the difference between accruals and rebate income from the partial settlement as well as the difference between the rebate income and the partial settlement.



SAP ECC menu Logistics Retailing Purchasing Subsequent settlement Vendor rebate arrangements Rebate Arrangement Create Settlement Document Via Report



Business role Retail Buyer Subsequent Settlement(SAP_NBPR_SUBSETTLEMENT_RT_S )

Business role menu Subsequent Settlement Subsequent Settlement Settlement re Vendor Rebate Arrs.



2. On the Settlement: Vendor Rebate Arrangement, Purchasing screen, make the following entries.


Rebate arrangements

Rebate arrangement see step 4.2.

Settlement date End-date of the arrangement for example, 31.12.2011





Condition records

Perform settlement accounting

select

3. Choose Execute.

4. Accept the message: Settlement date later than current date. Condition records may be settled prematurely! Perform settlement accounting anyway? by choosing Yes.

5. Set cursor on the first Partial settlement, and choose Sett.doc

6. The Choose settlement document screen appears. Choose the first document and choose Enter.

7. Choose Accounting to check the accounting document.

8. Choose Back.


Or


10. Ensure if all arrangements with your vendors have status D by using one of the following navigation options:


SAP ECC menu Logistics Retailing Master Data Conditions/ Arrangements Rebate Arrangements Arrangements, Purchasing Display





Business role menu Subsequent SettlementSubsequent SettlementDisplay Agreement

11. Choose F4. The Restrict Value Range screen appears.

12. On the Arrangements by condition granter tab, make the following entries.




Condition granter PCS-V141 (Fashion) PCS-V411 (Hard goods)

PCS-V331 (Food)

13. Choose Start Search.

14. Choose the existing arrangement with Enter.

15. On the Display Agreement screen, the Agreement number is displayed.

16. Choose Enter.

17. Check the status in the Agreement Status field (should be D = Final settlement of agreement already carried out).


Or

