New GL and Classic GL are two ways to implement General Ledger functionality in SAP ECC5 and

ECC6. New GL provides lot of benefits over classic GL. The New GL benefits

- Provide an extension to the existing functionality in classic GL, or

- Provide new functionality compared to classic GL, or

- Provide a technologically superior way to perform a functionality in Classic GL

It is imperative to understand the differences between Classic and New GL to be able to understand
which solution addresses the business requirements better. I am providing a comparative analysis of
the basic differences between Classic and New GL.

(1) Extended Data Structure provides flexibility

SAP has consolidated the multiple totals table (GLT0, GLPCT, etc) in classic GL into a single
FAGLFLEXT Totals table with New GL. One Summary Table provides flexibility and faster response
time for reporting. FAGLFLEXT can also be enhanced by adding customer defined fields.

(2) Segment Reporting to ensure Statutory Requirements

IAS accounting standards define the statutory requirements for segment reporting. New GL has
document splitting functionality that enables segment reporting. Standard Segment Reporting
functionality is not available in Classic GL.

(3) Real Time Integration between FI and CO

Classic GL has the period-close reconciliation ledger functionality to synchronize FI and CO for cost
transfers across functional area, business area and company code originating in CO. New GL has a
real-time integration between FI and CO that happens with each transaction originating in CO
instead of a summary posting done by reconciliation ledger during period-close.

(4) Parallel Accounting

New GL provides Non-leading ledgers for parallel accounting like IFRS and GAAP. Parallel
accounting can also be implemented using Account based approach which is also available in
classic GL.

(5) Reduce TCO by Faster Period Close Activities

Faster Period Close is possible with New GL as,

(a) Reconciliation Ledger is not required

(b) Balance sheet Adjustments are not required

(c) Profit and Loss Adjustment are not required

(d) Activities related to Special Purpose Ledger are not required

(e) Depreciation posting is online instead of a batch session

(6) Flexible Drill-down Reporting in New GL

New GL has advanced drill-down capabilities by segment and other characteristics.

OBYC Rule (Automatic Account Determination)

OBYC rule based on Five factor upon which system recognize that which GL should be posted in
case of inventory management and invoice posting relevant to financial and cost accounting. These
factors are:

 Chart of Account
 Valuation grouping Code
 Transaction Event Key
 Account Grouping
 Valuation Class

MATERIAL LEDGER:

http://www.erpfixers.com/blog/2016/11/28/so-whats-the-deal-with-material-ledger

How long does a Material Ledger project take?

A: This varies from company to company. It also depends on how many plants are being
activated. In my experience it has taken between 6 weeks and 4 months. It is important to
copy your production system into a sandbox and do several test iterations before going
live with ML. This is where most of the time is spent. Once you are comfortable with the
results you will find that the live run can be done within a short window.

Q: Does material ledger work with materials valued at moving average price?

A: Yes it works very well, the ML setup, requires a customizing set and a material master
data set. If the ML is active and you have a material with moving average as price
determination, the behavior of the system will be the same as a company without material
ledger. the advantage on that is to get the ML reports active also for the moving average
materials, such as ckm3.

Q: Why does Material Ledger not distribute some variances?

A: There are several reasons for this, some are:

1) No quantity in material when the price difference arrives

2) The price limiter quantity blocks the price difference to be absorbed by the material

3) Missing customizing for transfers

4) Invoice without goods receipt

these are some cases.

Q: Can we use Material Ledger without Actual Costing?

A: Yes, Material Ledger can be used for parallel valuation, parallel currencies and
transfer pricing, without the need for actual costing.

Q: What is the best where are you to get unit cost reports from ECC?

A: There are several reports in SAP to support the actual unit cost. With ma terial ledger
"on" a quick report is s_P_99_410000062. also you can build own reports using KKML
functionality that is a drill down reports for material ledger, similar to what you get with
CO-PA.

Q: Hoping to understand which countries require use of material ledger such as

Brazil?

A: I use to say that is not that material ledger is required, but actual costing is required.
So in this list I would add, Turkey, Russia, some latin American countries. One of the
main goals of material ledger is actual costing. but another big functionality is reporting.
So many companies are using ML for reporting purposes. Another functionality is to have
multiple material ledgers, it can be for legal requirements or even management.

Q: Which version of S/4HANA makes Material Ledger activation required?

A: Certainly the latest version of S/4 HANA (1610) makes Material Ledger required. Note
that this does not mean that you need to activate actual costing. Making material ledger
required means that during the conversion to S/4 HANA, the ML tables will be activated
and you can use parallel currencies/valuation. If you already have Actual Costing, this
will also be activated, but it is not compulsory if you do not have it.
Q: Do I really need ML active for S4 1511 or greater? I am using S4 Simple Finance
/ Central Finance to create a global ledger for my many other SAP ERP’s. This S4
will “consolidate” the financial information... there will be absolutely no MM
movements in it.

A: Yes the ML is active by default in S4. this is to bring reporting functionality to MM.
the idea is if your company does not require or use actual costing, ML will act like in
ECC when you have ML for materials V2 or S2. It will add the reporting functionality but
no ML posting will happen.

Q: In the case you mentioned to use to create a global ledger to consolidate other
companies, ML will not impact your need.

A: Yes you can use ML is one plant andnot in another. ( ML Setup is by valuation area
and not by company. This is what will happen:

If you transfer from one plant to another ( both with ML) you can set ML to carry the
price differences from one plant to another.

If you transfer from one plant with to another without, a price difference will be posted in
the Key OBYC-AUM.

So no big issue in having ML in one site and no ML in another. The loss is that in the site
without ML you will not have ML reporting functionalities such as CKM3 and KKML0.

Q: Can you use material ledger in some companies but not in other companies and
still perform intercompany direct shipments or plant transfer? other companies use
standard cost.

A: Yes you can use ML is one plant andnot in another. (ML Setup is by valuation area
and not by company) this is what will happen.

If you transfer from one plant to another ( both with ML) you can set ML to carry the
price differences from one plant to another.

If you transfer from one plant with to another without, a price difference will be posted in
the Key OBYC-AUM.

So no big issue in having ML in one site and no ML in another. The loss is that in the site
without ML you will not have ML reporting functionalities such as CKM3 and KKML0.

Q: Do we need to close Process Orders before activating ML (in a productive system)

and then reopen them?

A: It is advised by SAP to close Process Orders before activating material ledger. The
reason is because process order tables are not converted to ML tables ( the way PO
history tables are). therefore, if you do not close a process order before activating ML,
you could have some inconsistencies relating to parallel currencies/valuation. Please
note however, that based on some specific client requests, I have successfully activated
ML without closing all orders. Consider this to be a "Best Practice" advice, as opposed
to one which is absolutely required.

Q: What do you think are few specific key things that we need to keep in mind while
using ML pertaining to the type of Price Control - ML with MAP vs SP.

A: It depends on what you are using ML for. If you want to use it for parallel
currencies/valuation as well as actual costing, then you definitely need the materials
(semi-finished and finished) to be valued at standard cost (this is because moving
average price is already a type of actual cost). If you are only using ML for parallel
currencies/valuation, then you can have the materials valued at MAP only.

Q: What is the most important improvement in SAP when i update my system from
ECC 6.0 eph4 to Hana S4 in costing and ML?

A: There are several improvements: First it is much faster (of course!). Also, the steps of
single level PD, multilevel PD, Revaluation of Consumption, and WIP revaluation, are
all just one executable step. Also, the "Not Distributed" differences calculation logic has
been vastly improved. And it is easier to update the standard cost wi th the latest
calculated ML price.

Q: To start the ML function from existing single currency MM-setup, how will the
group or LC2 values be assigned? Using the Fx-table (OB08) or other method?

A: The currency definition of ML is OMX2. you can choose from company code and
controlling area currency, the FI currency it will take from the currency you have defined
for the company code, in new GL from additional currencies for company code. you can
also set different currencies in the customizing. It is important that at least one currency
is shared across all legal entities you want to set up material ledger. Usually as best
practice we set one of the currencies as the client currency, because this currency is
shared in all.

Q: Can ML-AVR be used or USGAAP reporting? Is it only a management reporting

tool or can be used for accounting?

A: Yes, ML AVR (Alternative Valuation Run) can be used for US GAAP reporting. In fact,
one of its key strengths is to calculate a separate Actual Cost for a separate accounting
principle (such as IAS vs. US GAAP). It can be used for both management and financial
reporting. For example you can use it to "smooth out" the varying actual prices over
several months, or you can use it to update a separate CO version. You have the choice o f
whether you want the results to be posted to FI or not.
Q: Is Material Ledger & Standard Costing mutually exclusive? i.e. If material A is
using Std Costing, then material A could NOT be used for ML?

A: For the material ledger setup there are 2 main steps:

1) Customizing the valuation area for material ledger

2) The second you define in the material master data, which material would be relevant
for material ledger.

The materials relevant for material ledger must be set as Standard and price
determination = 3 that means level and multilevel. if you set it to = 2, it will show in ML
reports, but all price differences ML will not consider. You will have the same as a
company running the system without ML with price determination Standard. the gain you
have in this scenario is that you can still using the ML reports for these materials. It Will
show all value flow for the material.

For material with "V" no change as well, same behavior with or without, with the benefit
of getting the ML reports also for the "V" material when material ledger is active.

Q: Would the previous question on process orders apply similarly to production

orders?

A: Yes, the question on process orders applies similarly to production orders as well. As
mentioned, it is a recommendation from SAP to close the orders, but from personal
experience (some customers kept orders open for several months at a time) I have found
that you can leave the orders open. I would recommend that, as part of your testing you
make sure that orders are settled as normal after your first ML conversion.

Q: Is ML-WIP step relevant in a ML-AVR run?

A: It depends. If you are using AVR to calculate actual costs for a different version (i.e. a
different accounting principle) then all the steps that are relevant in your n ormal ML run
should be relevant in your AVR run. Note however, that even in a normal ML run, you
may not find it necessary t use the WIP revaluation. In some countries it is required, but
from a management reporting perspective, it may not be.

Q: Any standard reports to help in reconciliation of GL with ML?

A: When you are converting to ML, one of the critical steps is to make sure that the G/L
and ML are reconciled. The are tools in the conversion process to make sure that this is
the case (CKMADJUST, for example). However, if you remember that ML is simply a
subsidiary ledger for Material Movement transactions, then you will realize that if MM is
reconciled to the G/L, then ML is also reconciled to the G/L. I would recommend 2
reports: the standard one is MB5L, and the newer one is FAGL_MM_RECON.
Q: I use Group Valuation and simply defined Company Code as my partner for
Partner Cost Component Split. I also activated an additional controlling area
currency cost component split for the Legal Costing Variant. I would like to
compare Group Valuation.

A: One good option you have is to create a KKML0 report, with an enhancement to bring
cost component split. and with this you can define one column of the report for one
currency and second column for another currency. Standard way is only in ckm3n one by
one.

Q: Can we change CCS (add more CC) in a live ML/AC environment?

A: Yes you can change it. It is always a good point of discussion. A change in CCS is ok
if you follow some recommendations. For example, if your cost component is called ZA
and you want to add more components on that. It is not ok to change the Za component.
What you must do is:

1) Create a new CCS with validity date in the beginning of the period.

2) Calculate a new STANDARD for all products you have to be released in the new
period

3) Settle all production order, that means no wip to following month

4) Leave both CCS active. the date you define in validity will be used by SAP which CCS
is valid

5) When a new period is open in MMPV SAP will update the table CKMKEV with the
CCS that will be used in each period. so if you open the period an later send the
customizing it will fail

6) You DON'T need to delete old data, doing this way you will keep your history

Q: If we use actual costing and the ML-active how much processing time to most
companies add to the month-end jobs? Assuming we are using this for a
consumption inventory (purchased items only) rather than manufacturing?

A: This really depends on how many materials/plants you have in your sys tem. To give a
rough guide (although every company is different), a client of mine (with mainly
purchased materials) has around 100,000 materials in around 20 plants, and the ML run
takes around 4 hours to complete.

Q: If using the Actual Costing process today for Brazil, Russia, and Turkey, will the
month-end closing steps continue to be necessary or will those types of activities
happen real-time?
A: If I understand correctly, I think you are asking whether any allocations that usually
happen at the end of the month will happen in realtime with Material Ledger activated. If
that is the case, the answer (for the most part) is no. Material Ledger does not eliminate
the need to run assessments, settlements, etc. at month end. In fact it relies on this data in
order to do a complete calculation. Please note that you can run material ledger before
the the month end as long as you do not execute the "Post Closing" step. That way you
can get a "feel" for where you will be at the end of the month. However, the info rmation
will not be complete until all the month end activities have taken place.

Q: If we convert to the ML does all PO creation need to be stopped until the

conversion. Or if the inventory is frozen-locked from processing can service order
PO still be processed?

A: Hi, in the process of activating ML, you will need a cutover at least to convert the
data. one of the steps it to run CKMSTART. SAP will convert the data for ML, Purchase
orders, Production orders, Order history, historical tables, and other. it will be
necessary a maintenance in the master data after conversion that is part of the cutover.
But this is not a stop for ML implemantation. Meaning companies with large amount of
data without ML can also acitvate ML without risk of loosing data.

Q: Will this conversion impact all MM-active plants or only the selected
plants?/companies converting to the ML?

A: Only in the plants you select in ckmstart. the others no. You need to wait until the data
is converted to work again with the plant. By default when you set a plant live in ckmstart
SAP sets the materials that were S, to S2 that means not relevant for level multilevel (No
ML relevant). The post processing step is to change the materials from 2 to 3 so ML will
also record price differences for the materials.

Q: If we want to activate a ML for and new MM-setup, company and plant, how
much time does testing take?

A: If a plant is not already on SAP and they want to go to ML, then there is no conversion
needed, therefore you only need to test the ML functionality itself. Again this varies
depending on the company, but I would allow 1 - 2 weeks of testing.

Q: Do either of our speakers have experience for Oil and Gas clients running the
MM?

A: Yes we have worked with oil and gas material ledger. there are some specific
functionalities, such as Distribution of usage variances and another add -ons as well that
will require a little bit more time for the project, because it depends how you are using
oil and gas. But the ML works fine with oil and gas as well. The restriction for ML is for
retail companies, but also for this there are some workarounds.
Q: Can you clarify the comment about ML with Moving Average and Price
Determination "2" is the same as not using ML at all? We do this and do see a
difference - a separate ML document is generated the records "variances" for the
adjustment in the moving average.

A: Yes it is the same, you see the ML posting because SAP automatic calculate the new
moving average for the product. it is a posting in and out, to make the Moving average.
The separated ML document is because in the customizing it was defined as ML
document. But you can also define this document as price difference. The important part
is that Moving average without ml = moving average with ML. the ad vantage is to use the
reports for ML when ML is active.

Q. How to BOM & Routing to a material?

Step1. Create Material MM01

Step2. Create BOM CS01

Step3. Create Rate Routing CA21

Step4. In MM02 for the above material, go to MRP4 View and click on production
version pushbutton, and give Version Number and description and the validity dates and
rem allowd indicator and then double click on the version line, it will take u to another
screen, there you Select rate routing and assign the group & group counter in Planning
Data and then in BOM Data u enter Alt BOM & BOM Usage details. For rem tick on
REM Allowed check box and then click on Check, if all the assignment is OK then it will
give you a message saying BOM & ROUTING available. Save the material master.

FI – MM INTERGRATION
Valuation area:
Stock of a material owned by a company is an asset to the company. Valuation area defines the
organization level at which materials are valuated.
SAP has provided two options for valuation.
1. Valuation at plant level: All materials are valuated at plant level.
2. Valuation at company code level: All materials in all plants of a company are valuated at company
code level.
This setting is defined in t-code OX14.
Valuated stock:
Total valuated stock = Stock in unrestricted use + Stock in transit between storage locations/warehouses
of a plant + Stock in quality inspection.
Material type:
This defines the type of material.
EG: Raw material, Finished goods etc.
Material type is defined during material master data creation.
Movement type:
This defines the type of material movement from one place to other. Movement type enables the system
to find predefined posting rules determining how the stock and consumption accounts are to be posted.
All possible goods movements are already defined by standard SAP
EG: Movement type 101 refers goods receipt
Movement type is entered while posting stock movement related transactions. Most of the time, standard
SAP automatically derives the movement type based on transaction code.
EG: If we go to MIGO, default movement type 101 is displayed by system.

Valuation class:
Valuation class is defined for the combination of plant and material (In Accounting 1 view of material
master).
Valuation class allows posting of stock values of
1. Materials of same material type to different G/L account (Different valuation class is assigned in
different plants for the same material)
2. Materials of different material type to same G/L account (Same valuation class is assigned to
materials of different material type)
Note: G/L accounts can be defined at valuation class level along with other parameters.
Valuation grouping code:
Valuation grouping code combines the valuation areas having same business properties for the account
determination. This reduces number of entries to be created for automatic account determination for the
stock postings.
EG: Valuation area 1 and 2 are required to be posted to same G/L account, these are grouped to
valuation grouping code ABC and G/L is determined based on valuation grouping code and valuation
class.
Before using valuation grouping code, it needs to be activated in OMWM.

Valuation grouping code is assigned to valuation area in t-code OMWD.

In below example, five valuation areas are assigned to same valuation grouping code.
Account modification/General modification:
This key is used to determine different G/L account for the same kind of goods movement based on origin
and target.
EG: During Goods issue, offsetting G/L is determined from transaction key GBB. If business wants to post
to different G/Ls for goods issue for cost centers (Movement type 201) and good issues to orders
(Movement type 261) for the same material and plant, Account modifier can help here. To understand this
better, let us go to t-code OMWN where we define the transaction key and account modification for the
movement type.
Transaction key which we see in OBYC is determined based on the movement type. In below screenshot,
you can see all parameters are same for movement type 201 and 261 except account modification.

Please read F1 help on different fields in this screen to know more about functionality of each field.
T-code OMWN:

When material document is posted with these movement types, offsetting account is determined from
transaction key GBB based on account modifier and valuation class.

From below screenshot, you can see that, different offsetting G/L account can be determined for the
same transaction key and valuation class.

By Default, Standard SAP defines account modification keys for below transaction keys. User defined
keys can also be defined and respective account determination settings can be maintained.

 GBB (offsetting entry for inventory posting)

 PRD (price differences)

  KON (consignment liabilities)

Below are the modification keys defined by SAP (Extracted from F1 help).

Modifiers for GBB

For the transaction/event GBB (offsetting entry for inventory posting), the following account groupings have already
been assigned to the relevant movement types:

 AUF: for goods receipts for production orders with account assignment
 BSA: for initial entries of stock balances
 INV: for expense/revenue from inventory differences
 VAX: for goods issues for sales orders without account assignment object
 VAY: for goods issues for sales orders with account assignment object
 VBO: for consumption from stock of material provided to vendor
 VBR: for internal goods issues (e.g., for cost center)
 VKA: for consumption for sales order without SD
 VNG: for scrapping/destruction
 VQP: for sampling
 ZOB: for goods receipts without purchase orders
 ZOF: for goods receipts without production orders

Modifiers for PRD

If you also activate account grouping for transaction/event PRD (price differences) when you make the settings for
automatic postings, the following account groupings are already assigned to the relevant movement types in the
standard:

 none for goods receipts and invoice receipts for purchase orders

 PRF: for goods receipts for production orders

 PRA: for goods issues and other goods movements

Modifiers for KON

If you also activate account grouping for transaction/event KON (consignment liabilities) when you make the settings
for automatic postings, the following account groupings are already assigned to the relevant movement types in the
standard:

 none for consignment liabilities

 PIP: for pipeline liabilities

How are the account determination attributes determined for each transaction
key/event?

Did you observe different set of fields appears for different transaction keys in OBYC while maintaining
G/L account? Yes. This is defined in Rules for the transaction key.

EG: Select transaction key AUM in OBYC and click on “Rules” in toolbar.
You can see that general modification and valuation modifier is active.

If you go to G/L account maintenance for this key, you would see the same fields.

Quick snap of MM-FI Integration process:

When we do material posting for a valuated material, below flow happens.
1. Movement type and other attributes like special stock indicator, movement indicator etc are determined
based on business transaction like goods receipt for PO, production order etc.(OMWN). This is defined by
standard SAP.
2. Transaction key/event and account modifier is identified based on movement type and other standard
attributes in step 1 (OMWN)
3. Valuation grouping code activation is checked from OMWM
4. If active, for the given valuation area, valuation grouping code is identified from OMWD
5. For the identified transaction or event, check if valuation grouping code is active or not in OBYC (Click
the rules button for the transaction key)
6. Valuation class is determined from material master.
7. Based on the above identified attributes, select the G/L account from OBYC.
If system can’t find any account for the found attributes, stock posting can’t be done and system through
clear error stating for which combination of attributes, G/L account is missing. Such errors are mostly
seen during go live/while posting to new materials due to missing G/L account maintenance or due to
incorrect valuation class in material master data.
Now you know the process, here is the short cut to find out G/L.
Account determination details are stored in table T030. If you want to know based on what details XXX
account is determined, simply give that G/L in T030 table in field KONTS. This gives the possible
combination of entries where this G/L is assigned. We can further drill down based on the filtered entries.

Please share your valuable feedback, thoughts and add additional information/corrections if any
Check out the next blog in this series.

MM-FI integration: Account determination simulator

DOCUMENT SPLITTING

 Passive Splitting – This type of splitting is mostly occurs when the payment transaction
is posted for a vendor invoice. Now system splits the payment document bases on how
the vendor invoice was split in place already.

 Active Splitting – In Active Splitting the document is split according to mySAP ERP
predefined rules. SAP almost supports all the business process transactions but if it
doesn’t suit to any requirement the own splitting rules can be created.

 Zero Balancing Splitting – When the amounts within financial documents are not able to
balance out to Debit of Profit Centre and Credit of Profit Centre which does not Net
Off as its own, SAP then automatically generates new line item to balance the
document. We will see the example in following section of this scenario.

 Item Category – Item category categorizes the general ledger accounts for document
splitting. In the configuration each GL account is assigned to item category. Just to
name a few like 01000 – Balance Sheet Account, 02000 – Customer, 03000 – Vendor and
so on.

 Business Transaction – Business transaction is real scenario of business processes

happens in organization such as vendor invoice, customer invoice etc.

 Business Transaction Variant – In the SAP, financial postings are derives the item
category for individual line item. Business transaction variant always works in
conjunction with business transaction where business transaction restricts the business
processes to be posted to. System validates a check all postings against the item
category to validate if these postings are allowed by splitting rule if not then
understand this failed.
  Document Splitting Method – Document splitting method works in combination with
business transaction and business transaction variant it determines the document
splitting rule.

 Document Splitting Rule: Document splitting rule determines which item categories will
be split and from which item categories it will derive the account assignment

Common errors encountered while executing F110 (APP) and resolutions are listed out here, hope
these are helpful to troubleshoot the errors.

1) No valid payment method found

Maintain payment method in vendor master or in the invoice. Payment method has to be maintained at either in
vendor master or in the vendor invoice

2) Company codes XXXX do not appear in proposal XX.XX.2011 XXXX( Run date & Identification)
Please check if you have any open items for the vendors or not for the dates you are running proposal. Check with
FBL1N report for the chosen vendor. This is telling you that F110 could not find any records that meet those criteria.
As it is a generic message and the error can be because of any reasons or combination of multiple reasons.

A review of the additional log should help you to identify exact reason for not selecting a particular invoice.

3) Payment in Currency XXX, payment method X: No valid payment procedure

The payment program could not find a combination of payment method and house bank account with which the
payment can be carried out.

You might have restricted the payments for a particular currency/ currencies; you may have to change currencies
restrictions if required.

4) Account XXXXXX XXXX (Vendor Account number and Company code) blocked by Payment proposal XX.XX.2011 XXXX
(Run Date & Id)
Once you make a proposal for a vendor, you cannot create another proposal for the same vendor unless and until
first one is completed i.e. payment run is over. Unless payment run is over, vendor is locked for another proposal

Option1: complete the earlier proposal and continue the current proposal

Option2: Delete the earlier proposal and continue the current proposal

5) Minimum amount has not been reached

If your vendor due amount is less than threshold minimum amount, then your invoice will go into exception list in
F110. That means that the amount less than the minimum amount specified in the configuration will not be paid.

Exception is that if the payment method is maintained in the invoice, system will not consider the minimum amounts.
That means you can pay the amounts less the minimum amount by giving the payment method at invoice level.

6) Account or Invoice is blocked for payment

Item is blocked for payment means that the Invoice is blocked for payment. You need to manually unblock the invoice
or wait for it to get unblocked. Account is blocked for deletion means that the vendor is blocked for payment remove
the block in XK02 transaction or see it is flagged for deletion in XK05

7) Required details are no maintained in Vendor Master

If you select the Street/PO Box Postal Code, Bank Account number as mandatory in the FBZP Configuration and
those details are not maintained in the vendor master system throws an error.

8) No pymt possible because items with a debit bal.still exist; see job log ( Contributed by Godavari SAP Ravi Sankar Venna)
If a vendor has debit balance, it will be shown under exception list with this message. Automatic payment program
will pay a vendor with credit balance only.

If there is a debit balance on vendor due to any down payment, that needs to be adjusted while making the payment
for invoice. Otherwise, only making payment to invoices would be incorrect and the down payment would remains the
same on the account.

Therefore, it needs to be configured in FBZP.

==> All Company Codes

Include the special G/L indicators to be paid. Then they will also be selected within the payment and the invoice
amount would be adjusted accordingly.

9) Withholding tax information missing from line items

This error is because, if we update some with-holding tax parameters in vendor master after posting some vendor
transactions.

In order to resolve this error, follow these steps:

1. Delete the payment proposal in F110 transaction in which the aforesaid error occurred.
2. Go to SAP transaction SA38 and enter the program name: RFWT0010
3. In the next screen, mention the affected vendor or range, mention your company code, mention the date
specifications, select following options as per your requirement
4. Add new with-holding tax types
5. Copy with holding tax codes from master record
6. Also down payment and partial payments with with holding tax codes
7. Do not enter withholding tax code
8. Delete w/tax no longer relevant.

Check the result in ‘TEST’ mode first and then do the update run.

Again generate the payment proposal in transaction F110 and now we can edit (reallocate) the items which were
affected earlier due to the withholding tax error.