BUS 2081-Preliminary posting
Hi Experts,
When we post invoice in background my workflow is called which initially checks whether the invoice is parked and complete then posts the invoice.
here my problem is when user posts the invoices only few invoices takes lots of time to post.
for example normally invoices posts in seconds but for few invoices it takes more than hour to post.
The func mod used to post the doc is" MRM_PARKED_INVOICE_POST".
I have checked for system load and other background jobs at that time no issues with the jobs and load.
Thanks,
Narmadha M.
Hi Narmadha,
The problem here i think is not duplicates. May be you are posting multiple invoices for single Purchasing Order Document. So the system puts on hold the invoice documents with the same PO and processes it during the next run of the background run for error Work Items.
Before you trigger your workflow you should first check whether the documents is locked or not and reprocess it again. Or you can schedule the job for executing error workitems very frequently.
May be this helps you out.
Regards
Gautam
Edited by: gautam maini on Nov 29, 2010 8:57 AM
Similar Messages
-
FB01 Preliminary posting by RFC
Hi experts,
I'm facing a problem with FB01 preliminary posting.
The situation is:
I have a system we will call A with BC component which can call RFC BAPI on SAP system that will called B.
On SAP system B, we can use FM PRELIMINARY_POSTING_FB01. But this FM is not an RFC function. So can't be used by system A.
have you any idea on how to resolve this problem?
Thank you in advance
RegardsThanks Chandra,
i've tried to develop an RFC function and call the FM PRELIMINARY_POSTING_FB01 internally.
The question i have is : Which parameters will i have as input and output for this Z RFC function?
The other question is : PRELIMINARY_POSTING_FB01 don't have return codes? How can i check execution status?
Thank you -
Preliminary Post in Tcode F-28
Nice day. I would like to know if there is any way to post in a preliminary manner through the transaction F-28.
Hi,
F-28 is a transaction for clearing, it is not possible to post a preliminary document.
you can use FV50,FV60,FV70 or F-63 FBV1 to create a preliminary document and post it in FBV0.
BR,
Gladys -
MIR7 preliminary posting - Entry date continuity after posting
Hi All,
Is anybody has experice regarding the following issue?
in MIR7 preliminary incoming invoice is created. E.g. Entry date (CPUDT) 20/02/2009. When the we post preliminary invoice, system updates CPUDT with the actual date, by this we lose continuity of incoming invoice numbering.
Thanx in advance.
AnettHi All,
Is anybody has experice regarding the following issue?
in MIR7 preliminary incoming invoice is created. E.g. Entry date (CPUDT) 20/02/2009. When the we post preliminary invoice, system updates CPUDT with the actual date, by this we lose continuity of incoming invoice numbering.
Thanx in advance.
Anett -
Are FW800 and FW400 Ports On Separate Buses...On Santa Rosa MBP?
Hi Folks,
I have yet to get a definitive answer from Apple Support, Apple store techs, the Web, searching these forums, etc. on this question:
On the latest MacBook Pro (Santa Rosa), are the Firewire 800 and Firewire 400 ports on separate buses? In other words, if I have an external FW400 drive (or other FW400 device such as an audio interface) running on the FW400 port, and an external FW800 drive running on the FW800 port, will the 800 run at 800 speeds or 400 speeds?
Here are the answers I've received thus far:
Apple Support: "Yes...they 'should' be on separate buses", "The techs say the 800 'should' run at 800", "You should call an Apple store"
Apple Store #1: "They ARE on separate buses"
Apple Store #2: "They ARE NOT on separate buses"
The Web: I've not found one source that supports that they ARE on separate buses. Every post I've read in this and other forums suggest that they share the same bus and that the FW800 port will degrade in this situation.
Does anyone have the definitive answer on this? Any real-world experience?
Thank you so much.
RichIgnore the previous poster.
Here is all you need to know...
There is ONE FireWire bus. It supports up to 800 MB/sec.
*You cannot use both the FW800 and FW400 ports at the same time! You can't!*
If you for example plug in a FireWire 800 hard drive into your FireWire 800 port, and a video camera into the FireWire 400 port, then capturing video in Final Cut Pro simply *WILL NOT WORK.*
So, what is the solution?
One solution is to plug the video camera into the hard drive, assuming it has a FW 400 port on it. This will daisy-chain the video camera through the FW 800 hard drive.
Another solution is to buy a FireWire ExpressCard for your 34mm ExpressCard slot. I got one with two FireWire 400 ports at NewEgg.com for $29.99. There are also ones available that have FireWire 800 ports on them, but they are pricier. Adding the ExpressCard gives you *an additional FireWire bus* that will have its own 800MB/s dedicated just to it. This is the best way to go since now you will have DUAL buses.
For example I hook my FireWire 800 hard drive up on my FW 800 port, and my MOTU 828 up on the ExpressCard FireWire 400 port. That way, the audio signals coming in are not clogging up the bus that the record drive is set up on... I've been able to get better latency for recording this way!
Hope this helps!! -
Dear all,
Can anyone give me the detailed explaination of MM-FI configuration or any links where we get the information about this please
Thanks & Regards
Somashekar AnandHi,
SAP Materials Managements
Relationship to Finance
Finance in Logistics
Finance in Logistics - A look from Materials Management
The purpose of this document is to explore the relationship materials management has with accounting in SAP. We will take three swipes at this relationship. First, at an overview level, we will consider a materials management workflow scenario. Next, we will dig deeper as we create documents to support that scenario, and consider the account postings made. Finally, we will consider configuration, and show how SAP automatically posted to various accounts.
A Materials Management Workflow Scenario
Lets consider the following map :
Starting from the top box, we see that a purchase requisition is created. This can be entered manually (as in the case if a secretary wants to order office supplies), or automatically via MRP (through Materials Requirements Planning, where material requirements are generated based on satisfying customer orders, production lines, and other needs). A purchase requisition would contain information about :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
A P.Req. may have to go through a release procedure in order to be converted into a purchase order. At this point, suffice it to say that SAP has ensured that employees do not get to acquire materials just because they have nice smiles.
Next, it is up to purchasing to determine a vendor for this requisition. In SAP, the purchasing department has several options : source lists, purchasing info records (material-vendor records), quota arrangements, and vendor master records. A vendor may also be selected based on price quotations attained by the purchasing department.
A purchase order may now be created. Note : in the standard configuration, a purchase requisition is not required in order to create a purchase order. The same information entered in the purchase requisition is entered in a purchase order (note items 1 through 6), plus a purchase order would have a specified vendor.
Purchase order follow-up depends on the purchasing organization. In some organizations, confirmation of a received PO is required. The confirmation could then be a signal to the receiving dock to expect goods on a certain date. Follow-up might include further negotiation, such as price, quantity, or delivery date changes.
A goods receipt for the purchase order is now entered. In the standard configuration, a goods receipt does not require a PO, or any other type of order. With valuated materials, a goods receipt will now cause an account entry. This account entry will typically be against a stock (or production/sales order) account and a clearing account. More about this later. Note that to the side, goods issues and transfer postings are shown. These are also functions of a warehouse, and both can cause account postings. It is important to understand which goods movements will affect accounting and how.
Often an invoice will be received with the goods shipment, but it can be received independently. Invoice verification is the process of determining whether an invoice matches what was received. In SAP, invoices can be entered either from materials management or from the accounts payable side. Most of us would hold that it is up to A/P to enter the invoice, but who better to verify the invoice against the goods shipment and quality than MM? This issue is up to the company and project team installing SAP. The account entries made upon invoice receipt will typically be against the clearing account posted when the goods received and the vendors account (indicating that the vendor should be paid). The invoice may be blocked for payment for various reasons (e.g.invoiced too early, wrong quantity), but even blocked invoices can cause account postings in SAP.
The invoice can now be paid. Invoice payment is done by A/P, outside of MM. This is done by means of payment programs where A/P clerks have the ability to select which vendors to pay, the means of payment, and whether or not to block payment (based on subsequent QI, or poor relations with the vendor). The account postings for payment are typically against the vendors account (signifying that payment is being received) and against cash (or a bank account).
The Documents
The purpose of this section is to show account postings which relate to documents created from materials management. This will include the creation of the following documents :
1. Purchase requisition
2. Purchase order
3. Goods receipt
4. Vendor invoice
Note that RFQs and quotations will not be considered. This is because neither of these documents has an account assignment category. Their only relevance to accounting is that they specify a material (and thus a material type), and the quotation specifies a vendor and a price. With no account assignment category, however, there is no specification as to who will pay for the ultimate purchase.
The purchase requisition
The purchase requisition is created through transaction ME51 (Log > MM > Purch > Req. > Create). As mentioned, the following are determined in a purchase requisition :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
This is shown on the following screen :
As mentioned, neither the vendor, nor the material price is specified in the requisition. A vendor can be specified in a requisition which has been "allocated", but thats a separate story.
The purchase requisition has no direct account postings. When a purchase order is created with reference to the requisition, the account assignment (category) and the material items are carried over. As of 2.2, the account assignment can be changed when the requisition is converted to a PO, but not the account assignment category. (You can change the account assignment from one cost center to another, but not from a cost center to a sales order -- different account assignment categories).
The purchase order
A purchase order can be created for a known vendor with the transaction code ME21 (accessed by Log>MM>Purchasing>Purchase Order>Create>Vendor known). An un-allocated (no vendor previously selected) purchase requisition might then be referenced. Alternatively, a purchase order can be created with reference to an allocated requisition using transaction code ME58 (Log>MM>Purchasing>Purchase Order>Create>via requisition).
As mentioned, the purchase order has the same entries as a requisition, plus item prices and a specified vendor. A sample purchase order is shown :
The purchase order has no direct account postings. However, account postings from goods receipts and invoices made against POs are very much affected by accounts designated in the POs. As of 2.2, a purchase orders account assignment can be changed as long as no goods have been received against the PO, and no invoice has been posted against it. (Thus, if no GR or invoice has been posted against a PO, the account assignment can be changed from one cost center to another, but not from a cost center to a sales order -- just like with requisitions).
The goods receipt (for a purchase order)
A goods receipt for a purchase order is created using transaction code MB01 (Log> MM>Inventory Management>Goods movement>Goods receipt>For purchase order). A movement type can then be selected via the menu bar, or using the list of possible entries. In SAP, every goods movement has a "movement type". The three headings of goods movements in SAP are good receipts, goods issues and transfer postings. Most goods movements will cause account postings. More will be said about that later.
With every goods movement (or transfer posting) in SAP, a material document is created. For every goods movement which affects a G/L account, an accounting document will be created (separate, but tied, to the material document). Material documents are not deleted, but they can be canceled or reversed. Thus, if a good receipt was posted with the wrong storage location and the wrong quantity, the receipt could be canceled. The cancellation will create a new material document (and probably an accounting document which will contain reverse debit/credit entries to what were entered in the first accounting document). Note, that if a goods receipt is entered for twenty-five pieces of a material, and only twenty pieces were actually received, a reversal could be entered. This reversal would be for five pieces. It would also have a material document, and the associated accounting document would have reverse debit/credit postings for the value of the five easy pieces.
The following is a goods receipt for the purchase order created in the last picture :
The movement type is one of the most important entries in materials management. It controls how account postings are made (as we will see), and it is very easy to overlook, as it is only a three-digit identifier. After several materials movements, one becomes familiar with common movement types (e.g. 101 - goods receipt of a PO, 201 - goods issue for a sales order, 561 - initial stock entry, and so on). The movement type will control the account postings with the aid of other parameters (such as the material type and the account assignment category).
The accounting view of the above transaction is shown in the following view :
Using the movement type (101), SAPs automatic account assignment was able to determine that a debit should be made to the cost centers account (which was specified on the purchase order), and the GR/IR clearing account should be credited. With automatic account assignment, the proper accounts with their respective "posting keys" were specified. Posting keys determine whether debits or credits are made against given accounts. More will be said about posting keys later.
The invoice (for a purchase order)
Invoices on the materials management side of SAP are entered via transaction code MRHR (Log>MM>Invoice verification>Document entry>Enter invoice). One could also enter credit memos in materials management (via a similar path to that just shown), as well as subsequent debits/credits against previous entries. As mentioned, these are usually entries made by accounts payable (A/P) clerks, but SAP allows its customers the option of entering this information in MM.
In SAP, invoices are not posted unless total debits and credits balance. New in 2.2, preliminary posted invoices can be made for invoices. In such a case, the proper PO to register the invoice against is unknown, therefore an A/P clerk can enter the invoice information, and "park" the document. Note that in "parked" invoices, no account postings are made.
Invoices can be blocked for payment because tolerances are exceeded. For example, the invoice date is much before the expected receiving date stated on a PO, thus date tolerance has been violated (it wouldnt be the first time a date was violated). Similarly, an invoice can be entered for a quantity greater than that which was received. Here the quantity tolerance has been violated. In SAP, even though an invoice is blocked for payment, account postings are made.
With goods movements, a material document is always created, and an associated accounting document is created when G/L accounts are affected. With invoices, one accounting document is created. An itemized listing of an invoice entered with reference to the PO created for this document is shown :
The accounts referenced in the above picture are not posted to until the invoice document has been saved. The "accounting view" of the above saved document is shown :
The accounting view of the invoice reflects what the item view showed, but note that the account entries could not be made unless the invoice balanced.
Also shown in the picture are tax codes. Tax codes can be created with a simple valuated entry (which would be manually maintained by A/P, purchasing, and system administrators). Tax codes can also be maintained via an external interface. In the US, tax codes are defined by :
1. the jurisdictional laws of the place to which the goods are shipped,
2. the material type of the goods being shipped, and
3. the taxability of the entity (customer) receiving the goods.
There are more than 50,000 different tax jurisdiction areas in the US (as they are defined by state, county, city, zip codes, etc.). External tax systems (such as AVP or Vertex) maintain the taxation rates for these jurisdictional areas. In 2.2, modifications have been created to interface external tax systems. In 3.0, this interface will be standard.
The account entries described in this section are shown in the following "T" account entries.
With the goods receipt, the debit to the cost center account (which could be the cost centers stock account) represents an increase in on-hand stock, while the credit to the GR/IR clearing account represents an outstanding invoice approval process.
With the invoice receipt, the invoice is verified that, in fact, the goods were received, and were of acceptable quality. This invoice entry creates a debit to the GR/IR clearing account (to balance the account), and a credit to the vendor account. A credit to vendor account signifies that in order to make the account balance, the vendor must be paid (debit the vendor account). Note that if the received goods were of sub-standard quality, payment could be blocked at this point by either not entering the invoice, or (more likely), the invoice would be entered, but blocked for payment. (Invoice verification is considered the third link of "three-way matching" -- the matching of the PO, GR and invoice. The invoice verifies the purchase order price and specifications, and that the goods in the PO were received and of appropriate quality)
The payment of the invoice is the final link in the workflow chain. The vendor is paid (account debited), and cash is decreased (credited). In SAP, maintenance of vendor payment is outside of materials management, but with an integrated system, it is coordinated.
Automatic Account Assignments in Materials Management
Consideration of automatic account assignments in MM will be approached in two steps, according to the accounting documents created in the last section. First, we will pursue the account postings made by goods movements, then we will consider account postings made by invoice entries.
Account postings through goods movements
Lets start from the basics. As mentioned, with each goods movement there can be an associated account posting. Where are these account postings maintained? A good place to first look is table 156s. This is accessed by table maintenance (SM31), entering "T156S", and hitting either the "Maintain" or "Display" button. The following table is then presented :
This table shows configuration information based on all the movement types (hundreds) in SAP. For our discussion on account postings, we do not need to concern ourselves now about the entries in the column and to the right of "SLoc".
From the fields shown, a quantity string and value string are determined. Note, that it is the combination of all the appropriate fields which makes this determination. The quantity string determines which quantity fields are updated (through a sequence of instructions), and the value string determines which account posting keys will be signaled (also through a sequence of instructions). Therefore, in order to determine which quantity string and value string are to be referenced for each goods movement, the significant fields of table 156S are now defined from left to right, the following fields have the following meaning :
Movement type - the three digit code associated with a goods movement. It must be specified with every goods movement.
Value update indicator - every material type is designated as to whether or not the material value is updated during goods movements. Thus, the value update indicator signifies if the account posting can affect the material account.
Quantity update indicator - every material type is also designated as to whether or not material quantities are to be updated during goods movements. Note that the the material types quantity update indicator and value update indicator must match a line entry in order to use the associated quantity and value strings.
Special stock indicator - this field indicates who owns the material and who gets the material. For example, the indicator might be blank (" "), where the stock is taken by the user in their plant. The indicator might be "K" (for consignment), where the vendor owns the material, but the stock is taken into the users plant.
Movement indicator - This specifies the type of order the goods movement might be against. For example, the movement could be with reference to a purchase order, a delivery note, or with no reference.
Receipt indicator - This field is currently not used. In the future, it is expected that specification will be possible to determine if this movement was for a stock transport order or an outside purchase order
Consumption posting indicator - this field is used in the case of goods receipts for purchase orders, and is defined from the account assignment category in the PO. Thus, in our previous example, the account assignment of "K" (for cost center) in the purchase order ensured that the receipt debited the cost centers account, and not the stock account.
So with the right combination of these seven (actually six) entries, we determine quantity and value strings. The quantity string is handled very similarly to the value string. Quantity strings are maintained in table 156M (accessed via SM31 and display/maintain "T156M"). In the last picture, the quantity string for the top entry is ME02. In table 156M, the quantity string indicates if orders are to be updated and other relevant quantity information. This table will not be analyzed here.
Value strings are handled in table 156W (accessed via SM31 with display/maintain "T156W"). The value string for the top entry in the last picture was WE06. Table 156W is shown :
The value string WE06 has two entries. These entries have different transaction/event keys (also called account keys). The transaction/event (t/e) keys specify the type of account to be posted to. These transaction/event keys are found in table 030. Thus, WE06 specifies that t/e key KBS will be referenced first, followed by key WRX. Lets look at table 030 (accessed through SM31, display/maintain "T030", and select group RMK; OR via the menu path Tools > Cust. > Config > Acc. > Fin. Acc. > Book. > Bus. trans. > Gen. Ledger > MM > Auto posting).
Paging down through this table we see that KBS signifies an account specified in a purchase order, and WRX signifies a GR/IR clearing account. If we double-click on (or choose) KBS, we are brought to the following screen :
So how do we know which posting key to take? Is this a debit or a credit? We look to table 156 (a.k.a. "T156) in SM31.
For movement type 101, we see that the first entry is "S" under D/C. This signifies that the first entry is to be a debit, thus the first t/e key (KBS in this case) is a debit. Therefore, we look to posting key 81.
Note the line "posting keys are independent of chart of accounts" in the screen for key KBS. Lets look at where posting keys are configured in transaction OB41 (in table TBSL through SM31, or via the menu path Tools > Cust > Config > Acc > Fin Acctg > Book > Bus trans > G/L > Control > Posting keys).
Posting key 81 shows a debit to a G/L account. Lets look into this...(double-click or choose posting key 81)
We see that this key causes a debit to the specified G/L account. Thus, an account was specified in the PO (since 101 was a GR for a PO), and by finding the value string in table 156S, then the appropriate transaction/event keys in table 156W, and then by digging into the t/e keys in table 030, we were able to determine the appropriate account postings. So that told us about the debit made, but what about WRX? Lets also look inside t/e key WRX in table 030 (we first must specify the chart of accounts, in this case CAUS) :
Here we see different postings, a valuation grouping code, an account modifier and a valuation class. Since the account modifier is not shown in this screen, well cross that bridge when we get to it. For now, lets look into the valuation grouping code. This is found in table 001K through SM31 (also available in transaction OMWD; Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct. det. > Val. area grouping).
.From this screen, we see that the valuation grouping code is used to group different valuation areas and/or different company codes together within a chart of accounts so that they have similar postings. So we understand the valuation grouping code, now how about that valuation class? Thats attained from the accounting view of the material master (for that specific valuation area).
For this material, the valuation class of 3000 is chosen. When this field is drilled into, we see that for this raw material, the system knew that only certain valuation classes were allowed. How did the system know which valuation classes were allowed for this material? It knew because when this material was created, a material type was chosen. Now on to material type configuration. This can be accessed via transaction code OMS2 (T>C>C>L>MM>Master data > material > control data > material type > click on change or display), select "ROH" (for raw materials), then click on the "account assignment" button. This shows the possible valuation classes assigned to the material types.
So for this raw material, the valuation class chosen was 3000. Therefore, back in table 030, for the t/e key WRX, using the valuation grouping code found in table 001K and the valuation class for the material (found in the material master), we can determine the GR/IR clearing account entry.
While were in the material type screen, lets look at one other thing -- quantity/value updating. From the last picture, click on the button labeled "quantity/value". The following screen appears :
Note that to restrict quantity or value updating of this material type, the button "in no valuation area" under the headings of quantity or value updating would be selected. Thus, FOR EACH MATERIAL TYPE, THIS IS WHERE WE DETERMINE IF THERE IS QUANTITY OR VALUE UPDATING.
Back to our example from II.3 (a goods receipt for a purchase order)
So guess what! With what weve covered in this section were ready to track down how our goods receipt posting in the last section happened as it did! Lets consider what we know about the goods movement :
1. It is a goods receipt for a PO -- movement type 101.
2. The PO had an account assignment category of "K", for a cost center and therefore is an item set for consumption.
3. The material used was a raw material with a valuation class of 3000.
4. For raw materials, there is both quantity and value updating.
5. It is "standard stock" item (no special stock type)
So lets look to table 156S ==>
We are looking for the entry which is the third from the top. It meets all the criteria. Therefore, we are looking to value string WE06 for answers WE06 is found in table 156W.
As we said about this screen, WE06 has only two t/e keys. We determined the account posting for KBS in the following way :
1. We found KBS in table 030
2. Under KBS, we saw that two posting keys were there, one for a debit, one for a credit
3. In table 156, we found that the first entry is a debit, thus we select posting key 81
4. Next we looked to table TBSL (in transaction code OB41), and chose posting key 81
5. There we saw that posting key 81 causes a debit to a prespecified G/L account (the cost center account specified on the purchase order)
We also determined the account posting for WRX in the following way :
1. We found WRX in table 030
2. Under WRX, we saw that we saw that we needed to specify a valuation grouping code and a valuation class in order to determine the proper GR/IR clearing account.
3. In table 001K, we saw that for our valuation area (US01) and our company code (US01), we have the valuation grouping code US01.
4. From the accounting view of our material master, we saw that our material has a valuation class of 3000 for the plant we are operating in (US01).
Therefore, in table 030, with a valuation grouping code of US01 and a valuation class of 3000, we have the GR/IR clearing account as account number 191100. This is shown in the accounting document created for the goods receipt.
A small change to the purchase order...
We said that a purchase order creates no direct account postings. However, they very much affect account postings for subsequent documents! In the purchase order of section II.2, what if we had chosen the account assignment category as being standard? Lets look again at table 156S.
In this case, we choose the top entry -- goods receipt for a PO, where there is no consumption specified. We are thus given the value string WE01. Lets look to table 156W.
Here we have 12 different posting keys! Note that there should always be more than one posting key for a goods movement because there should always be at least one debit and at least one credit. We saw that for movement type 101 (in table 156), the first entry is a debit. Thus, lets look to table 030 to see what a debit under posting key BSX does.
Again we see the valuation grouping code US01 and valuation class 3000, we have account 300000. This is exactly what we find with this goods receipt ==>
Offsetting entries for inventory postings (Key GBB)
One last point about automatic account assignments from materials movements.
One of the t/e keys definable for a value string is GBB. This is a key often associated with goods issues, but can be used whenever offsets are required for inventory. This key is maintained in table 156X, which is shown :
As we determined the quantity and value strings from table 156S, here we not only can find the value string, but also the account modifier. If we look in table 030, we see the t/e key GBB. When we choose that key, we find the following view :
Where in the t/e key screens of BSX and WRX we only had to know the valuation grouping code and the valuation class, here we also need the account modifier. This screen shows that a goods movement which has a valuation grouping code of US01, a valuation class of 7900 (commonly used for semi-finished goods), and an account modifier of AUF would have debit and credit postings made to account 895000.
An Easier Way...
To review, we recommend a way of determining account postings from goods movement documents :
1. Check table T156S for the appropriate movement type
2. Find the appropriate movement type and value string in table T156S based on :
a. if the material type is quantity and/or value updated
b. if the item has a special stock type
c. what type of movement is occurring
d. what type of account assignment the item might have (consumption, sales order,
e. stock account, etc.)
3. Based on the value string, check table T156W for the sequence of t/e keys accessed
4. Check table T156 to determine if the sequence from T156W begins with a debit or a credit
5. Check table 030 to see the possible postings for each of the t/e keys
a. for the t/e keys which have simple entries of posting keys (as with KBS), look to table TBSL to see what account this posting key affects
b. for the t/e keys which have a valuation grouping code, account modifier, and a valuation class specification, find the account by the following :
look to table 001K to find the valuation grouping code based on the appropriate valuation area and company code
look to table T156X if an account modifier must be checked
look to the accounting view in the material master to find the appropriate valuation class
To check the account postings, use transaction code OMWB (accessed via the path Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct determ > Auto posting > Simulate). Hit cancel (in 2.2) to get to the next screen, then hit the "Simulation" button choose a plant, material and a movement type, and hit the "Account assignment" button.
This is one way to check the configuration without creating all of the documents.
Postings from invoices
Account postings made by invoices are much easier to understand, but harder to examine, than goods movement account postings. With invoices and credit memos, there is an associated document type (note the initial screen of an invoice)
However, we can look at the posting keys for invoices we can expect to be affected. These are maintained with transaction code (accessed via the path : Tools > Cust > Config > Acctg > Fin Acctg > Book > Bus trans > Base params > Control > Posting keys). We are brought to the following screen :
We see that posting key 31 is an invoice in which we credit a vendor. Lets choose this key (or double-click on it).
We see that this is a credit to a vendor account. We also see that posting key 31 has a reverse posting key of 22. The previous screen showed that this is a reverse invoice receipt (different from a credit memo). A note about vendors -- in purchasing, vendors can be created with regard to purchasing, or centrally. If a vendor is created with regard to purchasing only, the vendor will not have accounting information maintained. Thus, the vendor would not bill in the SAP system. This is not to say that the vendor will not bill (we should be so lucky), just that it is not done in the SAP system. This might be for SAP users who are using an external system for accounting (or A/P only).
When a vendor is created, it is designated with an account group. The main functions of a vendor account group are :
1. to designate if the vendor is a one-time vendor
2. to specify the number range the vendor might be assigned to (to assign a vendor name)
3. to maintain screen control for vendor maintenance
Vendor account groups are maintained in transaction OBD3 (Tools > Cust > Config > Acctg > FI Acctg > Book > Master Recs > A/P > Control > Acct groups). If we choose LIFA (general vendors), we see the following :
The screen shows that the number range for LIFA is "XX" (transaction XKN1 shows this to signify external number assignment). The screen also shows that this is not a one-time vendor. If we double click on "Company code data", and double-click on "account management" in the next screen, we see how accounting fields for this vendor are maintained in the vendor master record.
If an invoice is created with reference to a purchase order, the account postings are already specified, as checking is done as to whether the goods have been received. Note that in creating an invoice, it is not necessary that an A/P clerk reference a PO (although it is advisable if known). If a PO is not reference, the A/P clerk must manually maintain account entries. These account entries have associated posting keys. For example, a freight charge might have a posting key of 50. This account can be seen in table 030. Likewise, unplanned delivery costs can be charged against the group receiving the goods.
During invoice entry, alternative account entries can be entered, either as debits or credits. Thus, account determination is made as the invoice is entered.
Postings from purchasing documents
One last note...
You may find that some account postings happen when referencing purchasing documents, and there is no reference to these postings in table T156S. For example, freight charges. They can be specified in a PO, but how does a goods receipt know to take the POs freight charge over to the account posting?
First, lets remember where freight postings are made in a purchase order. In the pricing condition record (note a special condition type) :
So the condition record of the screen shown has a condition type of FRA1, a percentage freight charge. Purchasing condition types are tied to account postings through PURCHASING configuration. Thus if we look into transaction M/08, yes with a "/" (Tools > Cust. > Config > Log > MM > Purch. > Functs. > Conds. > Pricing > Pricing Proc. > Pricing Proc.), we see the following screen :
If we now double-click on RM0000 (the first pricing procedure), page down to find FRA1, hit the "change view" button, we find the following screen :
Here we see that condition type FRA1 is tied to account key FR1. If we now look in table T030, double-click on "RMK" (MM postings), and double-click on FR1, we see that (in CAUS, for example), these freight postings are made to account number 192100.
Regards,
Archit -
PLEASE TELL ME ABOUT FI-MM INTEGRATION IN DETAIL.
PLEASE TELL ME ABOUT FI-MM INTEGRATION IN DETAIL.
Urgents
maheshHi mahesh.. the follwoing notes are very useful to u ...
Relationship to Finance
Finance in Logistics
Finance in Logistics - A look from Materials Management
The purpose of this document is to explore the relationship materials management has with accounting in SAP. We will take three swipes at this relationship. First, at an overview level, we will consider a materials management workflow scenario. Next, we will dig deeper as we create documents to support that scenario, and consider the account postings made. Finally, we will consider configuration, and show how SAP automatically posted to various accounts.
A Materials Management Workflow Scenario
Lets consider the following map :
Starting from the top box, we see that a purchase requisition is created. This can be entered manually (as in the case if a secretary wants to order office supplies), or automatically via MRP (through Materials Requirements Planning, where material requirements are generated based on satisfying customer orders, production lines, and other needs). A purchase requisition would contain information about :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
A P.Req. may have to go through a release procedure in order to be converted into a purchase order. At this point, suffice it to say that SAP has ensured that employees do not get to acquire materials just because they have nice smiles.
Next, it is up to purchasing to determine a vendor for this requisition. In SAP, the purchasing department has several options : source lists, purchasing info records (material-vendor records), quota arrangements, and vendor master records. A vendor may also be selected based on price quotations attained by the purchasing department.
A purchase order may now be created. Note : in the standard configuration, a purchase requisition is not required in order to create a purchase order. The same information entered in the purchase requisition is entered in a purchase order (note items 1 through 6), plus a purchase order would have a specified vendor.
Purchase order follow-up depends on the purchasing organization. In some organizations, confirmation of a received PO is required. The confirmation could then be a signal to the receiving dock to expect goods on a certain date. Follow-up might include further negotiation, such as price, quantity, or delivery date changes.
A goods receipt for the purchase order is now entered. In the standard configuration, a goods receipt does not require a PO, or any other type of order. With valuated materials, a goods receipt will now cause an account entry. This account entry will typically be against a stock (or production/sales order) account and a clearing account. More about this later. Note that to the side, goods issues and transfer postings are shown. These are also functions of a warehouse, and both can cause account postings. It is important to understand which goods movements will affect accounting and how.
Often an invoice will be received with the goods shipment, but it can be received independently. Invoice verification is the process of determining whether an invoice matches what was received. In SAP, invoices can be entered either from materials management or from the accounts payable side. Most of us would hold that it is up to A/P to enter the invoice, but who better to verify the invoice against the goods shipment and quality than MM? This issue is up to the company and project team installing SAP. The account entries made upon invoice receipt will typically be against the clearing account posted when the goods received and the vendors account (indicating that the vendor should be paid). The invoice may be blocked for payment for various reasons (e.g.invoiced too early, wrong quantity), but even blocked invoices can cause account postings in SAP.
The invoice can now be paid. Invoice payment is done by A/P, outside of MM. This is done by means of payment programs where A/P clerks have the ability to select which vendors to pay, the means of payment, and whether or not to block payment (based on subsequent QI, or poor relations with the vendor). The account postings for payment are typically against the vendors account (signifying that payment is being received) and against cash (or a bank account).
The Documents
The purpose of this section is to show account postings which relate to documents created from materials management. This will include the creation of the following documents :
1. Purchase requisition
2. Purchase order
3. Goods receipt
4. Vendor invoice
Note that RFQs and quotations will not be considered. This is because neither of these documents has an account assignment category. Their only relevance to accounting is that they specify a material (and thus a material type), and the quotation specifies a vendor and a price. With no account assignment category, however, there is no specification as to who will pay for the ultimate purchase.
The purchase requisition
The purchase requisition is created through transaction ME51 (Log > MM > Purch > Req. > Create). As mentioned, the following are determined in a purchase requisition :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
This is shown on the following screen :
As mentioned, neither the vendor, nor the material price is specified in the requisition. A vendor can be specified in a requisition which has been "allocated", but thats a separate story.
The purchase requisition has no direct account postings. When a purchase order is created with reference to the requisition, the account assignment (category) and the material items are carried over. As of 2.2, the account assignment can be changed when the requisition is converted to a PO, but not the account assignment category. (You can change the account assignment from one cost center to another, but not from a cost center to a sales order -- different account assignment categories).
The purchase order
A purchase order can be created for a known vendor with the transaction code ME21 (accessed by Log>MM>Purchasing>Purchase Order>Create>Vendor known). An un-allocated (no vendor previously selected) purchase requisition might then be referenced. Alternatively, a purchase order can be created with reference to an allocated requisition using transaction code ME58 (Log>MM>Purchasing>Purchase Order>Create>via requisition).
As mentioned, the purchase order has the same entries as a requisition, plus item prices and a specified vendor. A sample purchase order is shown :
The purchase order has no direct account postings. However, account postings from goods receipts and invoices made against POs are very much affected by accounts designated in the POs. As of 2.2, a purchase orders account assignment can be changed as long as no goods have been received against the PO, and no invoice has been posted against it. (Thus, if no GR or invoice has been posted against a PO, the account assignment can be changed from one cost center to another, but not from a cost center to a sales order -- just like with requisitions).
The goods receipt (for a purchase order)
A goods receipt for a purchase order is created using transaction code MB01 (Log> MM>Inventory Management>Goods movement>Goods receipt>For purchase order). A movement type can then be selected via the menu bar, or using the list of possible entries. In SAP, every goods movement has a "movement type". The three headings of goods movements in SAP are good receipts, goods issues and transfer postings. Most goods movements will cause account postings. More will be said about that later.
With every goods movement (or transfer posting) in SAP, a material document is created. For every goods movement which affects a G/L account, an accounting document will be created (separate, but tied, to the material document). Material documents are not deleted, but they can be canceled or reversed. Thus, if a good receipt was posted with the wrong storage location and the wrong quantity, the receipt could be canceled. The cancellation will create a new material document (and probably an accounting document which will contain reverse debit/credit entries to what were entered in the first accounting document). Note, that if a goods receipt is entered for twenty-five pieces of a material, and only twenty pieces were actually received, a reversal could be entered. This reversal would be for five pieces. It would also have a material document, and the associated accounting document would have reverse debit/credit postings for the value of the five easy pieces.
The following is a goods receipt for the purchase order created in the last picture :
The movement type is one of the most important entries in materials management. It controls how account postings are made (as we will see), and it is very easy to overlook, as it is only a three-digit identifier. After several materials movements, one becomes familiar with common movement types (e.g. 101 - goods receipt of a PO, 201 - goods issue for a sales order, 561 - initial stock entry, and so on). The movement type will control the account postings with the aid of other parameters (such as the material type and the account assignment category).
The accounting view of the above transaction is shown in the following view :
Using the movement type (101), SAPs automatic account assignment was able to determine that a debit should be made to the cost centers account (which was specified on the purchase order), and the GR/IR clearing account should be credited. With automatic account assignment, the proper accounts with their respective "posting keys" were specified. Posting keys determine whether debits or credits are made against given accounts. More will be said about posting keys later.
The invoice (for a purchase order)
Invoices on the materials management side of SAP are entered via transaction code MRHR (Log>MM>Invoice verification>Document entry>Enter invoice). One could also enter credit memos in materials management (via a similar path to that just shown), as well as subsequent debits/credits against previous entries. As mentioned, these are usually entries made by accounts payable (A/P) clerks, but SAP allows its customers the option of entering this information in MM.
In SAP, invoices are not posted unless total debits and credits balance. New in 2.2, preliminary posted invoices can be made for invoices. In such a case, the proper PO to register the invoice against is unknown, therefore an A/P clerk can enter the invoice information, and "park" the document. Note that in "parked" invoices, no account postings are made.
Invoices can be blocked for payment because tolerances are exceeded. For example, the invoice date is much before the expected receiving date stated on a PO, thus date tolerance has been violated (it wouldnt be the first time a date was violated). Similarly, an invoice can be entered for a quantity greater than that which was received. Here the quantity tolerance has been violated. In SAP, even though an invoice is blocked for payment, account postings are made.
With goods movements, a material document is always created, and an associated accounting document is created when G/L accounts are affected. With invoices, one accounting document is created. An itemized listing of an invoice entered with reference to the PO created for this document is shown :
The accounts referenced in the above picture are not posted to until the invoice document has been saved. The "accounting view" of the above saved document is shown :
The accounting view of the invoice reflects what the item view showed, but note that the account entries could not be made unless the invoice balanced.
Also shown in the picture are tax codes. Tax codes can be created with a simple valuated entry (which would be manually maintained by A/P, purchasing, and system administrators). Tax codes can also be maintained via an external interface. In the US, tax codes are defined by :
1. the jurisdictional laws of the place to which the goods are shipped,
2. the material type of the goods being shipped, and
3. the taxability of the entity (customer) receiving the goods.
There are more than 50,000 different tax jurisdiction areas in the US (as they are defined by state, county, city, zip codes, etc.). External tax systems (such as AVP or Vertex) maintain the taxation rates for these jurisdictional areas. In 2.2, modifications have been created to interface external tax systems. In 3.0, this interface will be standard.
The account entries described in this section are shown in the following "T" account entries.
With the goods receipt, the debit to the cost center account (which could be the cost centers stock account) represents an increase in on-hand stock, while the credit to the GR/IR clearing account represents an outstanding invoice approval process.
With the invoice receipt, the invoice is verified that, in fact, the goods were received, and were of acceptable quality. This invoice entry creates a debit to the GR/IR clearing account (to balance the account), and a credit to the vendor account. A credit to vendor account signifies that in order to make the account balance, the vendor must be paid (debit the vendor account). Note that if the received goods were of sub-standard quality, payment could be blocked at this point by either not entering the invoice, or (more likely), the invoice would be entered, but blocked for payment. (Invoice verification is considered the third link of "three-way matching" -- the matching of the PO, GR and invoice. The invoice verifies the purchase order price and specifications, and that the goods in the PO were received and of appropriate quality)
The payment of the invoice is the final link in the workflow chain. The vendor is paid (account debited), and cash is decreased (credited). In SAP, maintenance of vendor payment is outside of materials management, but with an integrated system, it is coordinated.
Automatic Account Assignments in Materials Management
Consideration of automatic account assignments in MM will be approached in two steps, according to the accounting documents created in the last section. First, we will pursue the account postings made by goods movements, then we will consider account postings made by invoice entries.
Account postings through goods movements
Lets start from the basics. As mentioned, with each goods movement there can be an associated account posting. Where are these account postings maintained? A good place to first look is table 156s. This is accessed by table maintenance (SM31), entering "T156S", and hitting either the "Maintain" or "Display" button. The following table is then presented :
This table shows configuration information based on all the movement types (hundreds) in SAP. For our discussion on account postings, we do not need to concern ourselves now about the entries in the column and to the right of "SLoc".
From the fields shown, a quantity string and value string are determined. Note, that it is the combination of all the appropriate fields which makes this determination. The quantity string determines which quantity fields are updated (through a sequence of instructions), and the value string determines which account posting keys will be signaled (also through a sequence of instructions). Therefore, in order to determine which quantity string and value string are to be referenced for each goods movement, the significant fields of table 156S are now defined from left to right, the following fields have the following meaning :
Movement type - the three digit code associated with a goods movement. It must be specified with every goods movement.
Value update indicator - every material type is designated as to whether or not the material value is updated during goods movements. Thus, the value update indicator signifies if the account posting can affect the material account.
Quantity update indicator - every material type is also designated as to whether or not material quantities are to be updated during goods movements. Note that the the material types quantity update indicator and value update indicator must match a line entry in order to use the associated quantity and value strings.
Special stock indicator - this field indicates who owns the material and who gets the material. For example, the indicator might be blank (" "), where the stock is taken by the user in their plant. The indicator might be "K" (for consignment), where the vendor owns the material, but the stock is taken into the users plant.
Movement indicator - This specifies the type of order the goods movement might be against. For example, the movement could be with reference to a purchase order, a delivery note, or with no reference.
Receipt indicator - This field is currently not used. In the future, it is expected that specification will be possible to determine if this movement was for a stock transport order or an outside purchase order
Consumption posting indicator - this field is used in the case of goods receipts for purchase orders, and is defined from the account assignment category in the PO. Thus, in our previous example, the account assignment of "K" (for cost center) in the purchase order ensured that the receipt debited the cost centers account, and not the stock account.
So with the right combination of these seven (actually six) entries, we determine quantity and value strings. The quantity string is handled very similarly to the value string. Quantity strings are maintained in table 156M (accessed via SM31 and display/maintain "T156M"). In the last picture, the quantity string for the top entry is ME02. In table 156M, the quantity string indicates if orders are to be updated and other relevant quantity information. This table will not be analyzed here.
Value strings are handled in table 156W (accessed via SM31 with display/maintain "T156W"). The value string for the top entry in the last picture was WE06. Table 156W is shown :
The value string WE06 has two entries. These entries have different transaction/event keys (also called account keys). The transaction/event (t/e) keys specify the type of account to be posted to. These transaction/event keys are found in table 030. Thus, WE06 specifies that t/e key KBS will be referenced first, followed by key WRX. Lets look at table 030 (accessed through SM31, display/maintain "T030", and select group RMK; OR via the menu path Tools > Cust. > Config > Acc. > Fin. Acc. > Book. > Bus. trans. > Gen. Ledger > MM > Auto posting).
Paging down through this table we see that KBS signifies an account specified in a purchase order, and WRX signifies a GR/IR clearing account. If we double-click on (or choose) KBS, we are brought to the following screen :
So how do we know which posting key to take? Is this a debit or a credit? We look to table 156 (a.k.a. "T156) in SM31.
For movement type 101, we see that the first entry is "S" under D/C. This signifies that the first entry is to be a debit, thus the first t/e key (KBS in this case) is a debit. Therefore, we look to posting key 81.
Note the line "posting keys are independent of chart of accounts" in the screen for key KBS. Lets look at where posting keys are configured in transaction OB41 (in table TBSL through SM31, or via the menu path Tools > Cust > Config > Acc > Fin Acctg > Book > Bus trans > G/L > Control > Posting keys).
Posting key 81 shows a debit to a G/L account. Lets look into this...(double-click or choose posting key 81)
We see that this key causes a debit to the specified G/L account. Thus, an account was specified in the PO (since 101 was a GR for a PO), and by finding the value string in table 156S, then the appropriate transaction/event keys in table 156W, and then by digging into the t/e keys in table 030, we were able to determine the appropriate account postings. So that told us about the debit made, but what about WRX? Lets also look inside t/e key WRX in table 030 (we first must specify the chart of accounts, in this case CAUS) :
Here we see different postings, a valuation grouping code, an account modifier and a valuation class. Since the account modifier is not shown in this screen, well cross that bridge when we get to it. For now, lets look into the valuation grouping code. This is found in table 001K through SM31 (also available in transaction OMWD; Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct. det. > Val. area grouping).
.From this screen, we see that the valuation grouping code is used to group different valuation areas and/or different company codes together within a chart of accounts so that they have similar postings. So we understand the valuation grouping code, now how about that valuation class? Thats attained from the accounting view of the material master (for that specific valuation area).
For this material, the valuation class of 3000 is chosen. When this field is drilled into, we see that for this raw material, the system knew that only certain valuation classes were allowed. How did the system know which valuation classes were allowed for this material? It knew because when this material was created, a material type was chosen. Now on to material type configuration. This can be accessed via transaction code OMS2 (T>C>C>L>MM>Master data > material > control data > material type > click on change or display), select "ROH" (for raw materials), then click on the "account assignment" button. This shows the possible valuation classes assigned to the material types.
So for this raw material, the valuation class chosen was 3000. Therefore, back in table 030, for the t/e key WRX, using the valuation grouping code found in table 001K and the valuation class for the material (found in the material master), we can determine the GR/IR clearing account entry.
While were in the material type screen, lets look at one other thing -- quantity/value updating. From the last picture, click on the button labeled "quantity/value". The following screen appears :
Note that to restrict quantity or value updating of this material type, the button "in no valuation area" under the headings of quantity or value updating would be selected. Thus, FOR EACH MATERIAL TYPE, THIS IS WHERE WE DETERMINE IF THERE IS QUANTITY OR VALUE UPDATING.
Back to our example from II.3 (a goods receipt for a purchase order)
So guess what! With what weve covered in this section were ready to track down how our goods receipt posting in the last section happened as it did! Lets consider what we know about the goods movement :
1. It is a goods receipt for a PO -- movement type 101.
2. The PO had an account assignment category of "K", for a cost center and therefore is an item set for consumption.
3. The material used was a raw material with a valuation class of 3000.
4. For raw materials, there is both quantity and value updating.
5. It is "standard stock" item (no special stock type)
So lets look to table 156S ==>
We are looking for the entry which is the third from the top. It meets all the criteria. Therefore, we are looking to value string WE06 for answers WE06 is found in table 156W.
As we said about this screen, WE06 has only two t/e keys. We determined the account posting for KBS in the following way :
1. We found KBS in table 030
2. Under KBS, we saw that two posting keys were there, one for a debit, one for a credit
3. In table 156, we found that the first entry is a debit, thus we select posting key 81
4. Next we looked to table TBSL (in transaction code OB41), and chose posting key 81
5. There we saw that posting key 81 causes a debit to a prespecified G/L account (the cost center account specified on the purchase order)
We also determined the account posting for WRX in the following way :
1. We found WRX in table 030
2. Under WRX, we saw that we saw that we needed to specify a valuation grouping code and a valuation class in order to determine the proper GR/IR clearing account.
3. In table 001K, we saw that for our valuation area (US01) and our company code (US01), we have the valuation grouping code US01.
4. From the accounting view of our material master, we saw that our material has a valuation class of 3000 for the plant we are operating in (US01).
Therefore, in table 030, with a valuation grouping code of US01 and a valuation class of 3000, we have the GR/IR clearing account as account number 191100. This is shown in the accounting document created for the goods receipt.
A small change to the purchase order...
We said that a purchase order creates no direct account postings. However, they very much affect account postings for subsequent documents! In the purchase order of section II.2, what if we had chosen the account assignment category as being standard? Lets look again at table 156S.
In this case, we choose the top entry -- goods receipt for a PO, where there is no consumption specified. We are thus given the value string WE01. Lets look to table 156W.
Here we have 12 different posting keys! Note that there should always be more than one posting key for a goods movement because there should always be at least one debit and at least one credit. We saw that for movement type 101 (in table 156), the first entry is a debit. Thus, lets look to table 030 to see what a debit under posting key BSX does.
Again we see the valuation grouping code US01 and valuation class 3000, we have account 300000. This is exactly what we find with this goods receipt ==>
Offsetting entries for inventory postings (Key GBB)
One last point about automatic account assignments from materials movements.
One of the t/e keys definable for a value string is GBB. This is a key often associated with goods issues, but can be used whenever offsets are required for inventory. This key is maintained in table 156X, which is shown :
As we determined the quantity and value strings from table 156S, here we not only can find the value string, but also the account modifier. If we look in table 030, we see the t/e key GBB. When we choose that key, we find the following view :
Where in the t/e key screens of BSX and WRX we only had to know the valuation grouping code and the valuation class, here we also need the account modifier. This screen shows that a goods movement which has a valuation grouping code of US01, a valuation class of 7900 (commonly used for semi-finished goods), and an account modifier of AUF would have debit and credit postings made to account 895000.
An Easier Way...
To review, we recommend a way of determining account postings from goods movement documents :
1. Check table T156S for the appropriate movement type
2. Find the appropriate movement type and value string in table T156S based on :
a. if the material type is quantity and/or value updated
b. if the item has a special stock type
c. what type of movement is occurring
d. what type of account assignment the item might have (consumption, sales order,
e. stock account, etc.)
3. Based on the value string, check table T156W for the sequence of t/e keys accessed
4. Check table T156 to determine if the sequence from T156W begins with a debit or a credit
5. Check table 030 to see the possible postings for each of the t/e keys
a. for the t/e keys which have simple entries of posting keys (as with KBS), look to table TBSL to see what account this posting key affects
b. for the t/e keys which have a valuation grouping code, account modifier, and a valuation class specification, find the account by the following :
look to table 001K to find the valuation grouping code based on the appropriate valuation area and company code
look to table T156X if an account modifier must be checked
look to the accounting view in the material master to find the appropriate valuation class
To check the account postings, use transaction code OMWB (accessed via the path Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct determ > Auto posting > Simulate). Hit cancel (in 2.2) to get to the next screen, then hit the "Simulation" button choose a plant, material and a movement type, and hit the "Account assignment" button.
This is one way to check the configuration without creating all of the documents.
Postings from invoices
Account postings made by invoices are much easier to understand, but harder to examine, than goods movement account postings. With invoices and credit memos, there is an associated document type (note the initial screen of an invoice)
However, we can look at the posting keys for invoices we can expect to be affected. These are maintained with transaction code (accessed via the path : Tools > Cust > Config > Acctg > Fin Acctg > Book > Bus trans > Base params > Control > Posting keys). We are brought to the following screen :
We see that posting key 31 is an invoice in which we credit a vendor. Lets choose this key (or double-click on it).
We see that this is a credit to a vendor account. We also see that posting key 31 has a reverse posting key of 22. The previous screen showed that this is a reverse invoice receipt (different from a credit memo). A note about vendors -- in purchasing, vendors can be created with regard to purchasing, or centrally. If a vendor is created with regard to purchasing only, the vendor will not have accounting information maintained. Thus, the vendor would not bill in the SAP system. This is not to say that the vendor will not bill (we should be so lucky), just that it is not done in the SAP system. This might be for SAP users who are using an external system for accounting (or A/P only).
When a vendor is created, it is designated with an account group. The main functions of a vendor account group are :
1. to designate if the vendor is a one-time vendor
2. to specify the number range the vendor might be assigned to (to assign a vendor name)
3. to maintain screen control for vendor maintenance
Vendor account groups are maintained in transaction OBD3 (Tools > Cust > Config > Acctg > FI Acctg > Book > Master Recs > A/P > Control > Acct groups). If we choose LIFA (general vendors), we see the following :
The screen shows that the number range for LIFA is "XX" (transaction XKN1 shows this to signify external number assignment). The screen also shows that this is not a one-time vendor. If we double click on "Company code data", and double-click on "account management" in the next screen, we see how accounting fields for this vendor are maintained in the vendor master record.
If an invoice is created with reference to a purchase order, the account postings are already specified, as checking is done as to whether the goods have been received. Note that in creating an invoice, it is not necessary that an A/P clerk reference a PO (although it is advisable if known). If a PO is not reference, the A/P clerk must manually maintain account entries. These account entries have associated posting keys. For example, a freight charge might have a posting key of 50. This account can be seen in table 030. Likewise, unplanned delivery costs can be charged against the group receiving the goods.
During invoice entry, alternative account entries can be entered, either as debits or credits. Thus, account determination is made as the invoice is entered.
Postings from purchasing documents
One last note...
You may find that some account postings happen when referencing purchasing documents, and there is no reference to these postings in table T156S. For example, freight charges. They can be specified in a PO, but how does a goods receipt know to take the POs freight charge over to the account posting?
First, lets remember where freight postings are made in a purchase order. In the pricing condition record (note a special condition type) :
So the condition record of the screen shown has a condition type of FRA1, a percentage freight charge. Purchasing condition types are tied to account postings through PURCHASING configuration. Thus if we look into transaction M/08, yes with a "/" (Tools > Cust. > Config > Log > MM > Purch. > Functs. > Conds. > Pricing > Pricing Proc. > Pricing Proc.), we see the following screen :
If we now double-click on RM0000 (the first pricing procedure), page down to find FRA1, hit the "change view" button, we find the following screen :
Here we see that condition type FRA1 is tied to account key FR1. If we now look in table T030, double-click on "RMK" (MM postings), and double-click on FR1, we see that (in CAUS, for example), these freight postings are made to account number 192100.
Give me points if u fit so...
Dasharathi -
hi all,
can any body tell me what is the integration of mm fi,
thanksHi
Check integration of MM to FI
MM peoples have no direct integration with CO
SAP Materials Managements
Relationship to Finance
Finance in Logistics
Finance in Logistics - A look from Materials Management
The purpose of this document is to explore the relationship materials management has with accounting in SAP. We will take three swipes at this relationship. First, at an overview level, we will consider a materials management workflow scenario. Next, we will dig deeper as we create documents to support that scenario, and consider the account postings made. Finally, we will consider configuration, and show how SAP automatically posted to various accounts.
A Materials Management Workflow Scenario
Lets consider the following map :
Starting from the top box, we see that a purchase requisition is created. This can be entered manually (as in the case if a secretary wants to order office supplies), or automatically via MRP (through Materials Requirements Planning, where material requirements are generated based on satisfying customer orders, production lines, and other needs). A purchase requisition would contain information about :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
A P.Req. may have to go through a release procedure in order to be converted into a purchase order. At this point, suffice it to say that SAP has ensured that employees do not get to acquire materials just because they have nice smiles.
Next, it is up to purchasing to determine a vendor for this requisition. In SAP, the purchasing department has several options : source lists, purchasing info records (material-vendor records), quota arrangements, and vendor master records. A vendor may also be selected based on price quotations attained by the purchasing department.
A purchase order may now be created. Note : in the standard configuration, a purchase requisition is not required in order to create a purchase order. The same information entered in the purchase requisition is entered in a purchase order (note items 1 through 6), plus a purchase order would have a specified vendor.
Purchase order follow-up depends on the purchasing organization. In some organizations, confirmation of a received PO is required. The confirmation could then be a signal to the receiving dock to expect goods on a certain date. Follow-up might include further negotiation, such as price, quantity, or delivery date changes.
A goods receipt for the purchase order is now entered. In the standard configuration, a goods receipt does not require a PO, or any other type of order. With valuated materials, a goods receipt will now cause an account entry. This account entry will typically be against a stock (or production/sales order) account and a clearing account. More about this later. Note that to the side, goods issues and transfer postings are shown. These are also functions of a warehouse, and both can cause account postings. It is important to understand which goods movements will affect accounting and how.
Often an invoice will be received with the goods shipment, but it can be received independently. Invoice verification is the process of determining whether an invoice matches what was received. In SAP, invoices can be entered either from materials management or from the accounts payable side. Most of us would hold that it is up to A/P to enter the invoice, but who better to verify the invoice against the goods shipment and quality than MM? This issue is up to the company and project team installing SAP. The account entries made upon invoice receipt will typically be against the clearing account posted when the goods received and the vendors account (indicating that the vendor should be paid). The invoice may be blocked for payment for various reasons (e.g.invoiced too early, wrong quantity), but even blocked invoices can cause account postings in SAP.
The invoice can now be paid. Invoice payment is done by A/P, outside of MM. This is done by means of payment programs where A/P clerks have the ability to select which vendors to pay, the means of payment, and whether or not to block payment (based on subsequent QI, or poor relations with the vendor). The account postings for payment are typically against the vendors account (signifying that payment is being received) and against cash (or a bank account).
The Documents
The purpose of this section is to show account postings which relate to documents created from materials management. This will include the creation of the following documents :
1. Purchase requisition
2. Purchase order
3. Goods receipt
4. Vendor invoice
Note that RFQs and quotations will not be considered. This is because neither of these documents has an account assignment category. Their only relevance to accounting is that they specify a material (and thus a material type), and the quotation specifies a vendor and a price. With no account assignment category, however, there is no specification as to who will pay for the ultimate purchase.
The purchase requisition
The purchase requisition is created through transaction ME51 (Log > MM > Purch > Req. > Create). As mentioned, the following are determined in a purchase requisition :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
This is shown on the following screen :
As mentioned, neither the vendor, nor the material price is specified in the requisition. A vendor can be specified in a requisition which has been "allocated", but thats a separate story.
The purchase requisition has no direct account postings. When a purchase order is created with reference to the requisition, the account assignment (category) and the material items are carried over. As of 2.2, the account assignment can be changed when the requisition is converted to a PO, but not the account assignment category. (You can change the account assignment from one cost center to another, but not from a cost center to a sales order -- different account assignment categories).
The purchase order
A purchase order can be created for a known vendor with the transaction code ME21 (accessed by Log>MM>Purchasing>Purchase Order>Create>Vendor known). An un-allocated (no vendor previously selected) purchase requisition might then be referenced. Alternatively, a purchase order can be created with reference to an allocated requisition using transaction code ME58 (Log>MM>Purchasing>Purchase Order>Create>via requisition).
As mentioned, the purchase order has the same entries as a requisition, plus item prices and a specified vendor. A sample purchase order is shown :
The purchase order has no direct account postings. However, account postings from goods receipts and invoices made against POs are very much affected by accounts designated in the POs. As of 2.2, a purchase orders account assignment can be changed as long as no goods have been received against the PO, and no invoice has been posted against it. (Thus, if no GR or invoice has been posted against a PO, the account assignment can be changed from one cost center to another, but not from a cost center to a sales order -- just like with requisitions).
The goods receipt (for a purchase order)
A goods receipt for a purchase order is created using transaction code MB01 (Log> MM>Inventory Management>Goods movement>Goods receipt>For purchase order). A movement type can then be selected via the menu bar, or using the list of possible entries. In SAP, every goods movement has a "movement type". The three headings of goods movements in SAP are good receipts, goods issues and transfer postings. Most goods movements will cause account postings. More will be said about that later.
With every goods movement (or transfer posting) in SAP, a material document is created. For every goods movement which affects a G/L account, an accounting document will be created (separate, but tied, to the material document). Material documents are not deleted, but they can be canceled or reversed. Thus, if a good receipt was posted with the wrong storage location and the wrong quantity, the receipt could be canceled. The cancellation will create a new material document (and probably an accounting document which will contain reverse debit/credit entries to what were entered in the first accounting document). Note, that if a goods receipt is entered for twenty-five pieces of a material, and only twenty pieces were actually received, a reversal could be entered. This reversal would be for five pieces. It would also have a material document, and the associated accounting document would have reverse debit/credit postings for the value of the five easy pieces.
The following is a goods receipt for the purchase order created in the last picture :
The movement type is one of the most important entries in materials management. It controls how account postings are made (as we will see), and it is very easy to overlook, as it is only a three-digit identifier. After several materials movements, one becomes familiar with common movement types (e.g. 101 - goods receipt of a PO, 201 - goods issue for a sales order, 561 - initial stock entry, and so on). The movement type will control the account postings with the aid of other parameters (such as the material type and the account assignment category).
The accounting view of the above transaction is shown in the following view :
Using the movement type (101), SAPs automatic account assignment was able to determine that a debit should be made to the cost centers account (which was specified on the purchase order), and the GR/IR clearing account should be credited. With automatic account assignment, the proper accounts with their respective "posting keys" were specified. Posting keys determine whether debits or credits are made against given accounts. More will be said about posting keys later.
The invoice (for a purchase order)
Invoices on the materials management side of SAP are entered via transaction code MRHR (Log>MM>Invoice verification>Document entry>Enter invoice). One could also enter credit memos in materials management (via a similar path to that just shown), as well as subsequent debits/credits against previous entries. As mentioned, these are usually entries made by accounts payable (A/P) clerks, but SAP allows its customers the option of entering this information in MM.
In SAP, invoices are not posted unless total debits and credits balance. New in 2.2, preliminary posted invoices can be made for invoices. In such a case, the proper PO to register the invoice against is unknown, therefore an A/P clerk can enter the invoice information, and "park" the document. Note that in "parked" invoices, no account postings are made.
Invoices can be blocked for payment because tolerances are exceeded. For example, the invoice date is much before the expected receiving date stated on a PO, thus date tolerance has been violated (it wouldnt be the first time a date was violated). Similarly, an invoice can be entered for a quantity greater than that which was received. Here the quantity tolerance has been violated. In SAP, even though an invoice is blocked for payment, account postings are made.
With goods movements, a material document is always created, and an associated accounting document is created when G/L accounts are affected. With invoices, one accounting document is created. An itemized listing of an invoice entered with reference to the PO created for this document is shown :
The accounts referenced in the above picture are not posted to until the invoice document has been saved. The "accounting view" of the above saved document is shown :
The accounting view of the invoice reflects what the item view showed, but note that the account entries could not be made unless the invoice balanced.
Also shown in the picture are tax codes. Tax codes can be created with a simple valuated entry (which would be manually maintained by A/P, purchasing, and system administrators). Tax codes can also be maintained via an external interface. In the US, tax codes are defined by :
1. the jurisdictional laws of the place to which the goods are shipped,
2. the material type of the goods being shipped, and
3. the taxability of the entity (customer) receiving the goods.
There are more than 50,000 different tax jurisdiction areas in the US (as they are defined by state, county, city, zip codes, etc.). External tax systems (such as AVP or Vertex) maintain the taxation rates for these jurisdictional areas. In 2.2, modifications have been created to interface external tax systems. In 3.0, this interface will be standard.
The account entries described in this section are shown in the following "T" account entries.
With the goods receipt, the debit to the cost center account (which could be the cost centers stock account) represents an increase in on-hand stock, while the credit to the GR/IR clearing account represents an outstanding invoice approval process.
With the invoice receipt, the invoice is verified that, in fact, the goods were received, and were of acceptable quality. This invoice entry creates a debit to the GR/IR clearing account (to balance the account), and a credit to the vendor account. A credit to vendor account signifies that in order to make the account balance, the vendor must be paid (debit the vendor account). Note that if the received goods were of sub-standard quality, payment could be blocked at this point by either not entering the invoice, or (more likely), the invoice would be entered, but blocked for payment. (Invoice verification is considered the third link of "three-way matching" -- the matching of the PO, GR and invoice. The invoice verifies the purchase order price and specifications, and that the goods in the PO were received and of appropriate quality)
The payment of the invoice is the final link in the workflow chain. The vendor is paid (account debited), and cash is decreased (credited). In SAP, maintenance of vendor payment is outside of materials management, but with an integrated system, it is coordinated.
Automatic Account Assignments in Materials Management
Consideration of automatic account assignments in MM will be approached in two steps, according to the accounting documents created in the last section. First, we will pursue the account postings made by goods movements, then we will consider account postings made by invoice entries.
Account postings through goods movements
Lets start from the basics. As mentioned, with each goods movement there can be an associated account posting. Where are these account postings maintained? A good place to first look is table 156s. This is accessed by table maintenance (SM31), entering "T156S", and hitting either the "Maintain" or "Display" button. The following table is then presented :
This table shows configuration information based on all the movement types (hundreds) in SAP. For our discussion on account postings, we do not need to concern ourselves now about the entries in the column and to the right of "SLoc".
From the fields shown, a quantity string and value string are determined. Note, that it is the combination of all the appropriate fields which makes this determination. The quantity string determines which quantity fields are updated (through a sequence of instructions), and the value string determines which account posting keys will be signaled (also through a sequence of instructions). Therefore, in order to determine which quantity string and value string are to be referenced for each goods movement, the significant fields of table 156S are now defined from left to right, the following fields have the following meaning :
Movement type - the three digit code associated with a goods movement. It must be specified with every goods movement.
Value update indicator - every material type is designated as to whether or not the material value is updated during goods movements. Thus, the value update indicator signifies if the account posting can affect the material account.
Quantity update indicator - every material type is also designated as to whether or not material quantities are to be updated during goods movements. Note that the the material types quantity update indicator and value update indicator must match a line entry in order to use the associated quantity and value strings.
Special stock indicator - this field indicates who owns the material and who gets the material. For example, the indicator might be blank (" "), where the stock is taken by the user in their plant. The indicator might be "K" (for consignment), where the vendor owns the material, but the stock is taken into the users plant.
Movement indicator - This specifies the type of order the goods movement might be against. For example, the movement could be with reference to a purchase order, a delivery note, or with no reference.
Receipt indicator - This field is currently not used. In the future, it is expected that specification will be possible to determine if this movement was for a stock transport order or an outside purchase order
Consumption posting indicator - this field is used in the case of goods receipts for purchase orders, and is defined from the account assignment category in the PO. Thus, in our previous example, the account assignment of "K" (for cost center) in the purchase order ensured that the receipt debited the cost centers account, and not the stock account.
So with the right combination of these seven (actually six) entries, we determine quantity and value strings. The quantity string is handled very similarly to the value string. Quantity strings are maintained in table 156M (accessed via SM31 and display/maintain "T156M"). In the last picture, the quantity string for the top entry is ME02. In table 156M, the quantity string indicates if orders are to be updated and other relevant quantity information. This table will not be analyzed here.
Value strings are handled in table 156W (accessed via SM31 with display/maintain "T156W"). The value string for the top entry in the last picture was WE06. Table 156W is shown :
The value string WE06 has two entries. These entries have different transaction/event keys (also called account keys). The transaction/event (t/e) keys specify the type of account to be posted to. These transaction/event keys are found in table 030. Thus, WE06 specifies that t/e key KBS will be referenced first, followed by key WRX. Lets look at table 030 (accessed through SM31, display/maintain "T030", and select group RMK; OR via the menu path Tools > Cust. > Config > Acc. > Fin. Acc. > Book. > Bus. trans. > Gen. Ledger > MM > Auto posting).
Paging down through this table we see that KBS signifies an account specified in a purchase order, and WRX signifies a GR/IR clearing account. If we double-click on (or choose) KBS, we are brought to the following screen :
So how do we know which posting key to take? Is this a debit or a credit? We look to table 156 (a.k.a. "T156) in SM31.
For movement type 101, we see that the first entry is "S" under D/C. This signifies that the first entry is to be a debit, thus the first t/e key (KBS in this case) is a debit. Therefore, we look to posting key 81.
Note the line "posting keys are independent of chart of accounts" in the screen for key KBS. Lets look at where posting keys are configured in transaction OB41 (in table TBSL through SM31, or via the menu path Tools > Cust > Config > Acc > Fin Acctg > Book > Bus trans > G/L > Control > Posting keys).
Posting key 81 shows a debit to a G/L account. Lets look into this...(double-click or choose posting key 81)
We see that this key causes a debit to the specified G/L account. Thus, an account was specified in the PO (since 101 was a GR for a PO), and by finding the value string in table 156S, then the appropriate transaction/event keys in table 156W, and then by digging into the t/e keys in table 030, we were able to determine the appropriate account postings. So that told us about the debit made, but what about WRX? Lets also look inside t/e key WRX in table 030 (we first must specify the chart of accounts, in this case CAUS) :
Here we see different postings, a valuation grouping code, an account modifier and a valuation class. Since the account modifier is not shown in this screen, well cross that bridge when we get to it. For now, lets look into the valuation grouping code. This is found in table 001K through SM31 (also available in transaction OMWD; Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct. det. > Val. area grouping).
.From this screen, we see that the valuation grouping code is used to group different valuation areas and/or different company codes together within a chart of accounts so that they have similar postings. So we understand the valuation grouping code, now how about that valuation class? Thats attained from the accounting view of the material master (for that specific valuation area).
For this material, the valuation class of 3000 is chosen. When this field is drilled into, we see that for this raw material, the system knew that only certain valuation classes were allowed. How did the system know which valuation classes were allowed for this material? It knew because when this material was created, a material type was chosen. Now on to material type configuration. This can be accessed via transaction code OMS2 (T>C>C>L>MM>Master data > material > control data > material type > click on change or display), select "ROH" (for raw materials), then click on the "account assignment" button. This shows the possible valuation classes assigned to the material types.
So for this raw material, the valuation class chosen was 3000. Therefore, back in table 030, for the t/e key WRX, using the valuation grouping code found in table 001K and the valuation class for the material (found in the material master), we can determine the GR/IR clearing account entry.
While were in the material type screen, lets look at one other thing -- quantity/value updating. From the last picture, click on the button labeled "quantity/value". The following screen appears :
Note that to restrict quantity or value updating of this material type, the button "in no valuation area" under the headings of quantity or value updating would be selected. Thus, FOR EACH MATERIAL TYPE, THIS IS WHERE WE DETERMINE IF THERE IS QUANTITY OR VALUE UPDATING.
Back to our example from II.3 (a goods receipt for a purchase order)
So guess what! With what weve covered in this section were ready to track down how our goods receipt posting in the last section happened as it did! Lets consider what we know about the goods movement :
1. It is a goods receipt for a PO -- movement type 101.
2. The PO had an account assignment category of "K", for a cost center and therefore is an item set for consumption.
3. The material used was a raw material with a valuation class of 3000.
4. For raw materials, there is both quantity and value updating.
5. It is "standard stock" item (no special stock type)
So lets look to table 156S ==>
We are looking for the entry which is the third from the top. It meets all the criteria. Therefore, we are looking to value string WE06 for answers WE06 is found in table 156W.
As we said about this screen, WE06 has only two t/e keys. We determined the account posting for KBS in the following way :
1. We found KBS in table 030
2. Under KBS, we saw that two posting keys were there, one for a debit, one for a credit
3. In table 156, we found that the first entry is a debit, thus we select posting key 81
4. Next we looked to table TBSL (in transaction code OB41), and chose posting key 81
5. There we saw that posting key 81 causes a debit to a prespecified G/L account (the cost center account specified on the purchase order)
We also determined the account posting for WRX in the following way :
1. We found WRX in table 030
2. Under WRX, we saw that we saw that we needed to specify a valuation grouping code and a valuation class in order to determine the proper GR/IR clearing account.
3. In table 001K, we saw that for our valuation area (US01) and our company code (US01), we have the valuation grouping code US01.
4. From the accounting view of our material master, we saw that our material has a valuation class of 3000 for the plant we are operating in (US01).
Therefore, in table 030, with a valuation grouping code of US01 and a valuation class of 3000, we have the GR/IR clearing account as account number 191100. This is shown in the accounting document created for the goods receipt.
A small change to the purchase order...
We said that a purchase order creates no direct account postings. However, they very much affect account postings for subsequent documents! In the purchase order of section II.2, what if we had chosen the account assignment category as being standard? Lets look again at table 156S.
In this case, we choose the top entry -- goods receipt for a PO, where there is no consumption specified. We are thus given the value string WE01. Lets look to table 156W.
Here we have 12 different posting keys! Note that there should always be more than one posting key for a goods movement because there should always be at least one debit and at least one credit. We saw that for movement type 101 (in table 156), the first entry is a debit. Thus, lets look to table 030 to see what a debit under posting key BSX does.
Again we see the valuation grouping code US01 and valuation class 3000, we have account 300000. This is exactly what we find with this goods receipt ==>
Offsetting entries for inventory postings (Key GBB)
One last point about automatic account assignments from materials movements.
One of the t/e keys definable for a value string is GBB. This is a key often associated with goods issues, but can be used whenever offsets are required for inventory. This key is maintained in table 156X, which is shown :
As we determined the quantity and value strings from table 156S, here we not only can find the value string, but also the account modifier. If we look in table 030, we see the t/e key GBB. When we choose that key, we find the following view :
Where in the t/e key screens of BSX and WRX we only had to know the valuation grouping code and the valuation class, here we also need the account modifier. This screen shows that a goods movement which has a valuation grouping code of US01, a valuation class of 7900 (commonly used for semi-finished goods), and an account modifier of AUF would have debit and credit postings made to account 895000.
An Easier Way...
To review, we recommend a way of determining account postings from goods movement documents :
1. Check table T156S for the appropriate movement type
2. Find the appropriate movement type and value string in table T156S based on :
a. if the material type is quantity and/or value updated
b. if the item has a special stock type
c. what type of movement is occurring
d. what type of account assignment the item might have (consumption, sales order,
e. stock account, etc.)
3. Based on the value string, check table T156W for the sequence of t/e keys accessed
4. Check table T156 to determine if the sequence from T156W begins with a debit or a credit
5. Check table 030 to see the possible postings for each of the t/e keys
a. for the t/e keys which have simple entries of posting keys (as with KBS), look to table TBSL to see what account this posting key affects
b. for the t/e keys which have a valuation grouping code, account modifier, and a valuation class specification, find the account by the following :
look to table 001K to find the valuation grouping code based on the appropriate valuation area and company code
look to table T156X if an account modifier must be checked
look to the accounting view in the material master to find the appropriate valuation class
To check the account postings, use transaction code OMWB (accessed via the path Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct determ > Auto posting > Simulate). Hit cancel (in 2.2) to get to the next screen, then hit the "Simulation" button choose a plant, material and a movement type, and hit the "Account assignment" button.
This is one way to check the configuration without creating all of the documents.
Postings from invoices
Account postings made by invoices are much easier to understand, but harder to examine, than goods movement account postings. With invoices and credit memos, there is an associated document type (note the initial screen of an invoice)
However, we can look at the posting keys for invoices we can expect to be affected. These are maintained with transaction code (accessed via the path : Tools > Cust > Config > Acctg > Fin Acctg > Book > Bus trans > Base params > Control > Posting keys). We are brought to the following screen :
We see that posting key 31 is an invoice in which we credit a vendor. Lets choose this key (or double-click on it).
We see that this is a credit to a vendor account. We also see that posting key 31 has a reverse posting key of 22. The previous screen showed that this is a reverse invoice receipt (different from a credit memo). A note about vendors -- in purchasing, vendors can be created with regard to purchasing, or centrally. If a vendor is created with regard to purchasing only, the vendor will not have accounting information maintained. Thus, the vendor would not bill in the SAP system. This is not to say that the vendor will not bill (we should be so lucky), just that it is not done in the SAP system. This might be for SAP users who are using an external system for accounting (or A/P only).
When a vendor is created, it is designated with an account group. The main functions of a vendor account group are :
1. to designate if the vendor is a one-time vendor
2. to specify the number range the vendor might be assigned to (to assign a vendor name)
3. to maintain screen control for vendor maintenance
Vendor account groups are maintained in transaction OBD3 (Tools > Cust > Config > Acctg > FI Acctg > Book > Master Recs > A/P > Control > Acct groups). If we choose LIFA (general vendors), we see the following :
The screen shows that the number range for LIFA is "XX" (transaction XKN1 shows this to signify external number assignment). The screen also shows that this is not a one-time vendor. If we double click on "Company code data", and double-click on "account management" in the next screen, we see how accounting fields for this vendor are maintained in the vendor master record.
If an invoice is created with reference to a purchase order, the account postings are already specified, as checking is done as to whether the goods have been received. Note that in creating an invoice, it is not necessary that an A/P clerk reference a PO (although it is advisable if known). If a PO is not reference, the A/P clerk must manually maintain account entries. These account entries have associated posting keys. For example, a freight charge might have a posting key of 50. This account can be seen in table 030. Likewise, unplanned delivery costs can be charged against the group receiving the goods.
During invoice entry, alternative account entries can be entered, either as debits or credits. Thus, account determination is made as the invoice is entered.
Postings from purchasing documents
One last note...
You may find that some account postings happen when referencing purchasing documents, and there is no reference to these postings in table T156S. For example, freight charges. They can be specified in a PO, but how does a goods receipt know to take the POs freight charge over to the account posting?
First, lets remember where freight postings are made in a purchase order. In the pricing condition record (note a special condition type) :
So the condition record of the screen shown has a condition type of FRA1, a percentage freight charge. Purchasing condition types are tied to account postings through PURCHASING configuration. Thus if we look into transaction M/08, yes with a "/" (Tools > Cust. > Config > Log > MM > Purch. > Functs. > Conds. > Pricing > Pricing Proc. > Pricing Proc.), we see the following screen :
If we now double-click on RM0000 (the first pricing procedure), page down to find FRA1, hit the "change view" button, we find the following screen :
Here we see that condition type FRA1 is tied to account key FR1. If we now look in table T030, double-click on "RMK" (MM postings), and double-click on FR1, we see that (in CAUS, for example), these freight postings are made to account number 192100.
Vishal... -
Vipin,
Find the config below
1.Activate the New General Ledger Accounting by a single click on the clock icon
2.You will reach to change view "activation of New GL A/cg" detail screen and tick the checkbox and save.
3. After activation of New General Ledger Accounting, you exit the IMG screen When you re-enter , you find that a new node is added Financial Accounting (New)
4.After activation of New General Ledger Accounting , a new sub node appears in the IMG structure.
This sub node is Define Segment
The menu path is:
SAP Customizing IMG ---> Enterprise Structure -
> Definition ---> Financial Accounting ---> Define Segment
In this IMG activity, you define your segments.
If you then define your profit centers, you can enter an associated segment in the master record of a profit center. The segment is then derived from the assigned profit center during posting.
5.Activation has created a new field in Profit Center Master Record : the SEGMENT
6.Leading and Non- Leading Ledgers
In General Ledger Accounting , you can use several Ledgers in parallel. This allows you to produce financial statements according to different accounting principles. A ledger uses several dimensions from the totals table it is based upon. When defining Ledgers , one must be defined as the Leading Ledger . The Leading Ledger is based on the same accounting principles as that of the consolidated financial statements. It is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes. In each company code, the Leading Ledger receives exactly the same settings that apply to that company code : the currencies, the fiscal year variant and posting period variant .
You must designate one of your ledgers as the Leading Ledger. It is not possible to designate more than one ledger as the leading ledger.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define Ledgers for General Ledger Accounting
Clicking on the checkbox identifies one of your ledgers as the Leading Ledger.
7. Activation of Non Leading Ledgers
Non Leading Ledgers are parallel ledgers to the Leading Ledger . They can be based on local accounting principle, for example. You have to activate a non- Leading Ledger for individual company codes. Non- Leading Ledgers can have different fiscal year variants and posting period variants per company code to the Leading Ledger of this company code.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define and Activate Non Leading Ledgers
8.Assign scenarios to ledgers
A Scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in General Ledger Accounting, such as cost Center update or Profit Center update .You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled with posting data from other application components.
SAP delivers a number of scenarios in the standard system. It is not possible to create additional scenarios.
The menu path is:
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Fields -
> Display Scenarios for General Ledger Accounting.
9. Cost of sales accounting
Cost of sales accounting is a way to create a profit and loss statement (P&L) for a company by comparing the revenues to the costs or expenses incurred to obtain these revenues.
The expenses are mainly divided by functional area such as:
Manufacturing
Administration
Sales
Research and Development
We can activate Cost of Sales Accounting by the following menu path :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Ledger------> Activate Cost of Sales Accounting
Accounting transactions list
F-01 Enter Sample Document
F-02 Enter G/L Account Posting
F-03 Clear G/L Account
F-04 Post with Clearing
F-05 Post Foreign Currency Valuation
F-06 Post Incoming Payments
F-07 Post Outgoing Payments
F-18 Payment with Printout
F-19 Reverse Statistical Posting
F-20 Reverse Bill Liability
F-21 Enter Transfer Posting
F-22 Enter Customer Invoice
F-23 Return Bill of Exchange Pmt Request
F-25 Reverse Check/Bill of Exch.
F-26 Incoming Payments Fast Entry
F-27 Enter Customer Credit Memo
F-28 Post Incoming Payments
F-29 Post Customer Down Payment
F-30 Post with Clearing
F-31 Post Outgoing Payments
F-32 Clear Customer
F-33 Post Bill of Exchange Usage
F-34 Post Collection
F-35 Post Forfaiting
F-36 Bill of Exchange Payment
F-37 Customer Down Payment Request
F-38 Enter Statistical Posting
F-39 Clear Customer Down Payment
F-40 Bill of Exchange Payment
F-41 Enter Vendor Credit Memo
F-42 Enter Transfer Posting
F-43 Enter Vendor Invoice
F-44 Clear Vendor
F-46 Reverse Refinancing Acceptance
F-47 Down Payment Request
F-48 Post Vendor Down Payment
F-49 Customer Noted Item
F-51 Post with Clearing
F-52 Post Incoming Payments
F-53 Post Outgoing Payments
F-54 Clear Vendor Down Payment
F-55 Enter Statistical Posting
F-56 Reverse Statistical Posting
F-57 Vendor Noted Item
F-58 Payment with Printout
F-59 Payment Request
F-60 Maintain Table: Posting Periods
F-62 Maintain Table: Exchange Rates
F-63 Park Vendor Invoice
F-64 Park Customer Invoice
F-65 Preliminary Posting
F-66 Park Vendor Credit Memo
F-67 Park Customer Credit Memo
F-90 Acquisition from purchase w. vendor
F-91 Asset acquis. to clearing account
F-92 Asset Retire. frm Sale w/ Customer
F.01 ABAP/4 Report: Balance Sheet
F.02 Compact Journal
F.03 Reconciliation
F.04 G/L: Create Foreign Trade Report
F.05 Foreign Currency Val.: Open Items
F.06 Foreign Currency Valuation:G/L Assts
F.07 G/L: Balance Carried Forward
F.08 G/L: Account Balances
F.09 G/L: Account List
F.0A G/L: FTR Report on Disk
F.0B G/L: Create Z2 to Z4
F.10 G/L: Chart of Accounts
F.11 G/L: General Ledger from Doc.File
F.12 Advance Tax Return
F.13 ABAP/4 Report: Automatic Clearing
F.14 ABAP/4 Report: Recurring Entries
F.15 ABAP/4 Report: List Recurr.Entries
F.16 ABAP/4 Report: G/L Bal.Carried Fwd
F.17 ABAP/4 Report: Cust.Bal.Confirmation
F.18 ABAP/4 Report: Vend.Bal.Confirmation
F.19 G/L: Goods/Invoice Received Clearing
F.1A Customer/Vendor Statistics
F.1B Head Office and Branch Index
F.20 A/R: Account List
F.21 A/R: Open Items
F.22 A/R: Open Item Sorted List
F.23 A/R: Account Balances
F.24 A/R: Interest for Days Overdue
F.25 Bill of Exchange List
F.26 A/R: Balance Interest Calculation
F.27 A/R: Periodic Account Statements
F.28 Customers: Reset Credit Limit
F.29 A/R: Set Up Info System 1
F.2A Calc.cust.int.on arr.: Post (w/o OI)
F.2B Calc.cust.int.on arr.: Post(with OI)
F.2C Calc.cust.int.on arr.: w/o postings
F.2D Customrs: FI-SD mast.data comparison
F.2E Reconciliation Btwn Affiliated Comps
F.2F Management Acct Group Reconciliation
F.2G Create Account Group Reconcil. G/L
F.30 A/R: Evaluate Info System
F.31 Credit Management - Overview
F.32 Credit Management - Missing Data
F.33 Credit Management - Brief Overview
F.34 Credit Management - Mass Change
F.35 Credit Master Sheet
F.36 Adv.Ret.on Sls/Pur.Form Printout(DE)
F.37 Adv.rept.tx sls/purch.form print (BE
F.38 Transfer Posting of Deferred Tax
F.39 C FI Maint. table T042Z (BillExcTyp)
F.40 A/P: Account List
F.41 A/P: Open Items
F.42 A/P: Account Balances
F.44 A/P: Balance Interest Calculation
F.45 A/P: Set Up Info System 1
F.46 A/P: Evaluate Info System
F.47 Vendors: calc.of interest on arrears
F.48 Vendors: FI-MM mast.data comparison
F.4A Calc.vend.int.on arr.: Post (w/o OI)
F.4B Calc.vend.int.on arr.: Post(with OI)
F.4C Calc.vend.int.on arr.: w/o postings
F.50 G/L: Profitability Segment Adjustmnt
F.51 G/L: Open Items
F.52 G/L: Acct Bal.Interest Calculation
F.53 G/L: Account Assignment Manual
F.54 G/L: Structured Account Balances
F.56 Delete Recurring Document
F.57 G/L: Delete Sample Documents
F.58 OI Bal.Audit Trail: fr.Document File
F.59 Accum.Clas.Aud.Trail: Create Extract
F.5A Accum.Clas.Aud.Trail: Eval.Extract
F.5B Accum.OI Aud.Trail: Create Extract
F.5C Accum.OI Audit Trail: Display Extr.
F.5D G/L: Update Bal. Sheet Adjustment
F.5E G/L: Post Balance Sheet Adjustment
F.5F G/L: Balance Sheet Adjustment Log
F.5G G/L: Subseq.Adjustment(BA/PC) Sp.ErA
F.5I G/L: Adv.Rep.f.Tx on Sls/Purch.w.Jur
F.61 Correspondence: Print Requests
F.62 Correspondence: Print Int.Documents
F.63 Correspondence: Delete Requests
F.64 Correspondence: Maintain Requests
F.65 Correspondence: Print Letters (Cust)
F.66 Correspondence: Print Letters (Vend)
F.70 Bill/Exchange Pmnt Request Dunning
F.71 DME with Disk: B/Excha. Presentation
F.75 Extended Bill/Exchange Information
F.77 C FI Maintain Table T045D
F.78 C FI Maintain Table T045B
F.79 C FI Maintain Table T045G
F.80 Mass Reversal of Documents
F.81 Reverse Posting for Accr./Defer.Docs
F.90 C FI Maintain Table T045F
F.91 C FI Maintain Table T045L
F.92 C FI Maintain T012K (Bill/Exch.)
F.93 Maintain Bill Liability and Rem.Risk
F.97 General Ledger: Report Selection
F.98 Vendors: Report Selection
F.99 Customers: Report Selection
FB00 Accounting Editing Options
FB01 Post Document
FB02 Change Document
FB03 Display Document
FB03Z Display Document/Payment Usage
FB04 Document Changes
FB05 Post with Clearing
FB05_OLD Post with clearing
FB07 Control Totals
FB08 Reverse Document
FB09 Change Line Items
FB10 Invoice/Credit Fast Entry
FB11 Post Held Document
FB12 Request from Correspondence
FB13 Release for Payments
FB1D Clear Customer
FB1K Clear Vendor
FB1S Clear G/L Account
FB21 Enter Statistical Posting
FB22 Reverse Statistical Posting
FB31 Enter Noted Item
FB41 Post Tax Payable
FB50 G/L Acct Pstg: Single Screen Trans.
FB60 Enter Incoming Invoices
FB65 Enter Incoming Credit Memos
FB70 Enter Outgoing Invoices
FB75 Enter Outgoing Credit Memos
FB99 Check if Documents can be Archived
FBA1 Customer Down Payment Request
FBA2 Post Customer Down Payment
FBA3 Clear Customer Down Payment
FBA6 Vendor Down Payment Request
FBA7 Post Vendor Down Payment
FBA7_OLD Post Vendor Down Payment
FBA8 Clear Vendor Down Payment
FBA8_OLD Clear Vendor Down Payment
FBB1 Post Foreign Currency Valn
FBBA Display Acct Determination Config.
FBBP Maintain Acct Determination Config.
FBCJ Cash Journal
FBCJC0 C FI Maintain Tables TCJ_C_JOURNALS
FBCJC1 Cash Journal Document Number Range
FBCJC2 C FI Maint. Tables TCJ_TRANSACTIONS
FBCJC3 C FI Maintain Tables TCJ_PRINT
FBCOPY Copy Function Module
FBD1 Enter Recurring Entry
FBD2 Change Recurring Entry
FBD3 Display Recurring Entry
FBD4 Display Recurring Entry Changes
FBD5 Realize Recurring Entry
FBD9 Enter Recurring Entry
FBDF Menu Banque de France
FBE1 Create Payment Advice
FBE2 Change Payment Advice
FBE3 Display Payment Advice
FBE6 Delete Payment Advice
FBE7 Add to Payment Advice Account
FBF1 C80 Reporting Minus Sp.G/L Ind.
FBF2 Financial Transactions
FBF3 Control Report
FBF4 Download Documents
FBF5 Reports Minus Vendor Accounts
FBF6 Document Changes
FBF7 C80 Reports Minus Sp.G/L Ind.
FBF8 C84 Reports
FBFT Customizing BDF
FBIPU Maintain bank chains for partner
FBKA Display Accounting Configuration
FBKF FBKP/Carry Out Function (Internal)
FBKP Maintain Accounting Configuration
FBL1 Display Vendor Line Items
FBL1N Vendor Line Items
FBL2 Change Vendor Line Items
FBL2N Vendor Line Items
FBL3 Display G/L Account Line Items
FBL3N G/L Account Line Items
FBL4 Change G/L Account Line Items
FBL4N G/L Account Line Items
FBL5 Display Customer Line Items
FBL5N Customer Line Items
FBL6 Change Customer Line Items
FBL6N Customer Line Items
FBM1 Enter Sample Document
FBM2 Change Sample Document
FBM3 Display Sample Document
FBM4 Display Sample Document Changes
FBMA Display Dunning Procedure
FBME Banks
FBMP Maintain Dunning Procedure
FBN1 Accounting Document Number Ranges
FBN2 Number Range Maintenance: FI_PYORD
FBP1 Enter Payment Request
FBR1 Post with Reference Document
FBR2 Post Document
FBRA Reset Cleared Items
FBRC Reset Cleared Items (Payment Cards)
FBS1 Enter Accrual/Deferral Doc.
FBTA Display Text Determin.Configuration
FBTP Maintain Text Determin.Configuration
FBU2 Change Intercompany Document
FBU3 Display Intercompany Document
FBU8 Reverse Cross-Company Code Document
FBV0 Post Parked Document
FBV1 Park Document
FBV2 Change Parked Document
FBV3 Display Parked Document
FBV4 Change Parked Document (Header)
FBV5 Document Changes of Parked Documents
FBV6 Parked Document $
FBVB Post Parked Document
FBW1 Enter Bill of Exchange Pmnt Request
FBW2 Post Bill of Exch.acc.to Pmt Request
FBW3 Post Bill of Exchange Usage
FBW4 Reverse Bill Liability
FBW5 Customer Check/Bill of Exchange
FBW6 Vendor Check/Bill of Exchange
FBW7 Bank file to file system (for FBWD)
FBW8 File to Bank (for Transaction FBWD)
FBW9 C FI Maintain Table T045DTA
FBWA C FI Maintain Table T046a
FBWD Returned Bills of Exchange Payable
FBWD2 Parameter Transaction for FBWD
FBWE Bill/Exch.Presentatn - International
FBWQ C FI Maintain Table T045T
FBWR C FI Maintain Table T045W
FBWS C FI Maintain Table T046s
FBZ0 Display/Edit Payment Proposal
FBZ1 Post Incoming Payments
FBZ2 Post Outgoing Payments
FBZ3 Incoming Payments Fast Entry
FBZ4 Payment with Printout
FBZ5 Print Check For Payment Document
FBZ8 Display Payment Run
FBZA Display Pmnt Program Configuration
FBZG Failed Customer Payments
FBZP Maintain Pmnt Program Configuration
FK01 Create Vendor (Accounting)
FK02 Change Vendor (Accounting)
FK02CORE Maintain vendor
FK03 Display Vendor (Accounting)
FK04 Vendor Changes (Accounting)
FK05 Block Vendor (Accounting)
FK06 Mark Vendor for Deletion (Acctng)
FK08 Confirm Vendor Individually (Acctng)
FK09 Confirm Vendor List (Accounting)
FK10 Vendor Account Balance
FK10N Vendor Balance Display
FK10NA Vendor Balance Display
FK15 Transfer vendor changes: receive
FK16 Transfer vendor changes: receive
FKI0 Execute Report
FKI1 Create Report
FKI2 Change Report
FKI3 Display Report
FKI4 Create Form
FKI5 Change Form
FKI6 Display Form
FKIB Background Processing
FKIC Maintain Currency Translation Type
FKIK Maintain Key Figures
FKIM Report Monitor
FKIO Transport Reports
FKIP Transport Forms
FKIQ Import Reports from Client 000
FKIR Import Forms from Client 000
FKIT Translation Tool - Drilldown Report.
FKIV Maintain Global Variable
FKIX Reorganize Drilldown Reports
FKIY Reorganize Report Data
FKIZ Reorganize Forms
FKMT FI Acct Assignment Model Management
FS00 G/L acct master record maintenance
FS01 Create Master Record
FS02 Change Master Record
FS02CORE Maintain G/L account
FS03 Display Master Record
FS04 G/L Account Changes (Centrally)
FS05 Block Master Record
FS06 Mark Master Record for Deletion
FS10 G/L Account Balance
FS10N Balance Display
FS10NA Balance Display
FS15 Copy G/L account changes: Send
FS16 Copy G/L account changes: Receive
FSAA Display Address for Bal.Confirmatns
FSAP Addresses for Balance Confirmations
FSAV Balance Confirmations: Reply View
FSE2 Change Financial Statement Version
FSE3 Display Financial Statement Version
FSE4 Planning Preparation
FSE5 Maintain Planning
FSE5N Maintain Planning
FSE6 Display Planning
FSE6N Display Planning
FSE7 Maint.Fin.Statemnt Forgn Lang.Texts
FSE8 Display Forgn Lang Fin.Statmnt Texts
FSE9 Automatic Financial Statement Form
FSF1 Financial Calendar
FSI0 Execute report
FSI1 Create Report
FSI2 Change Report
FSI3 Display Report
FSI4 Create Form
FSI5 Change Form
FSI6 Display Form
FSIB Background processing
FSIC Maintain Currency Translation Type
FSIG Balance Sheet Reports Criteria Group
FSIK Maintain Key Figures
FSIM Report Monitor
FSIO Transport reports
FSIP Transport forms
FSIQ Import reports from client 000
FSIR Import forms from client 000
FSIT Translation Tool - Drilldown Report.
FSIV Maintain Global Variable
FSIX Reorganize Drilldown Reports
FSIY Reorganize report data
FSIZ Reorganize forms
FSK2 Maintain Sample Rules
FSK2_OLD Maintain Sample Rules
FSKB G/L Account Posting
FSM1 Create Sample Account
FSM2 Change Sample Account
FSM3 Display Sample Account
FSM4 Sample Account Changes
FSM5 Delete Sample Account
FSO2 Change Finan.Statement Vers. (old)
FSO3 Display Finan.Statement Vers. (Old)
FSP0 G/L acct master record in chrt/accts
FSP1 Create Master Record in Chart/Accts
FSP2 Change Master Record in Chart/Accts
FSP3 Display Master Record in Chart/Accts
FSP4 G/L Account Changes in Chart/Accts
FSP5 Block Master Record in Chart/Accts
FSP6 Mark Mast.Rec.for Del.in Chart/Accts
FSRD Loans Regulatory Reporting CH
FSRG Money Mkt Regulatory Reporting CH
FSRW Securities Regulatory Reporting CH
FSS0 G/L account master record in co code
FSS1 Create Master Record in Company Code
FSS2 Change Master Record in Company Code
FSS3 Display Master Record in Comp.Code
FSS4 G/L Account Changes in Company Code
FSSA Display Bal.Confirmatns Sel.Criteria
FSSP Change Bal.Confirmatns Sel.Criteria
FST0 G/L account record translation
FST2 Maintain Account Name
FST3 Display Account Name
OB00 C FI Maintain Table T030 (RDF)
OB01 C FI Maintain Table T691A
OB02 C FI Maintain Table T024B
OB03 C FI Maintain Table T003
OB04 C FI Maintain Table T030F
OB05 C FI Maintain Table T001S
OB06 C FI Maintain Table T031S
OB07 C FI Maintain table TCURV
OB08 C FI Maintain table TCURR
OB09 C FI Maintain Table T030H
OB10 C FI Maintain Table T049L
OB11 C FI Maintain Table T018P
OB12 C FI Maintain Table T691B
OB13 C FI Maintain Table T004
OB14 Configure Field Status Definition
OB15 C FI Maintain Table T004R
OB16 C FI Maintain Table TZUN/TZUNT
OB17 C FI Maintain Table T040
OB18 C FI Maintain Table T040S
OB19 C FI Maintain Table T059M
OB1A C FI Maint. Table T004 (Layouts)
OB1B C FI Maint. Table T004 (Layouts)
OB20 C FI Maintain Table T078D
OB21 C FI Maintain Table T079D
OB22 C FI Maintain Table T001A
OB23 C FI Maintain Table T078K
OB24 C FI Maintain Table T079K
OB25 C FI Maintain Table T001X
OB26 C FI Maintain Table T078S
OB27 C FI Maintain Table T008
OB28 C FI Maintain Table T001D
OB29 C FI Fiscal Year Variants
OB30 Accts Rec: Allocate flds -> fld gps
OB31 C FI Maintain Table T055G
OB32 C FI Maintain Table TBAER
OB33 C FI Maintain Table T055
OB34 C FI Maintain Table T055G
OB35 Customer Balance Confirmation
OB36 Vendor Balance Confirmation
OB37 C FI Maintain Table T001 (PERIV)
OB38 Assign Co.Code -> Cred.Cntl Area
OB39 C FI Maintain Table TRAS
OB40 C FI Maintain Table T030
OB41 Maintain Accounting Keys
OB42 C FI Maintain Table T056Z
OB43 C FI Maintain Table T015L
OB44 C FI Maintain Table T016
OB45 C FI Maintain Table T014
OB46 C FI Maintain Table T056
OB47 C FI Maintain Table T015W
OB48 C FI Maintain Matchcode SAKO
OB49 C FI Maintain Matchcode DEBI
OB50 C FI Maintain Matchcode KRED
OB51 C FI Maintain Table T024P
OB52 C FI Maintain Table T001B
OB53 C FI Maintain Table T030
OB54 C FI Maintain Table T001 (PERIV)
OB55 C FI Maintain Table TFAV
OB56 C FI Maintain Table T053
OB57 C FI Maintain Table T043
OB58 C FI Maintain Table T011/T011T
OB59 C FI Maintain Table T044A
OB60 C FI Maintain Table T041B
OB61 C FI Maintain Table T047M
OB62 C FI Maintain Table T001 (KTOPL + 2)
OB63 C FI Maintain Table T001 (XGJRV)
OB64 C FI Maintain Table T001 (WAABV)
OB65 C FI Maintain Table T001 (XGSBE)
OB66 C FI Maintain Table T001 (XKDFT)
OB67 C FI Maintain Table T001 (MREGL)
OB68 C FI Maintain Table T001
OB69 C FI Maintain Table T001
OB70 C FI Maintain Table T001
OB71 C FI Maintain Table T001
OB72 C FI Maintain Table T001O
OB73 C FI Maintain Table T031
OB74 C FI Maintain Table TF123
OB75 C FI Maintain Table T042D
OB76 C FI Maintain Table T045E
OB77 C FI Maintain Table T048/T048T
OB78 C FI Maintain Table T048B
OB79 C FI Maintain Table T048I
OB80 C FI Maintain Table T043K
OB81 C FI Maintain Table T056A
OB82 C FI Maintain Table T056U
OB83 C FI Maintain Table T056P
OB84 C FI Maintain Table T056D
OB85 C FI Maintain Table T056B
OB86 C FI Maintain Table T005 (WECHF)
OB87 C FI Maintain Table T001N
OB88 C FI Maintain Table T001
OB89 C FI Maintain Table T030
OB90 C FI Maintain Table T001R
OB91 C FI Maintain Table T001F
OB92 C FI Maintain Table T001G
OB93 C FI Maintain Table TGSBG
OB94 C FI Maintain Table T042M
OB95 C FI Maintain Table T042N
OB96 C FI Maintain Table T001F
OB97 C FI Maintain Table T059A
OB98 C FI Maintain Table T059F
OB99 C FI Maintain Table T005Q
OBA0 G/L Account Tolerance Groups
OBA1 C FI Maintain Table T030
OBA2 C FI Maintain Table T001M
OBA3 C FI Maintain Table T043G
OBA4 C FI Maintain Table T043T
OBA5 Change Message Control
OBA6 C FI Maintain Table T046
OBA7 C FI maintain table T003
OBA8 C FI Maintain Table TRERI
OBA9 C FI Maintain Table T015Z
OBAA C FI Maintain Table T056S
OBAB C FI Maintain Table T056Y
OBAC C FI Maintain Table T056R
OBAD C FI Maintain Table T005P
OBAE C FI Maintain Table T005S
OBAF C FI Maintain Table T048K
OBAG C FI Maintain Table T060O
OBAH C FI Maintain Table T060A
OBAI C FI Maintain Table T060
OBAJ C FI Maintain Table T060
OBAK C FI Maintain Table T060
OBAL C FI Maintain Table T052A
OBAM C FI Maintain Table T052R
OBAN C FI Maintain Table T060O
OBAO C FI Maintain Table T060O
OBAP C FI Maintain Table TZGR
OBAQ C FI Maintain Table T047R
OBAR C FI Maintain Table T077D
OBAS C FI Maintain Table T077K
OBAT C FI Maintain Table T055G
OBAU C FI Maintain Table T055
OBAV C FI Maintain Table T049E
OBAW C FI Maintain Table T049F
OBAX C FI Maintain Table T049A
OBAY C FI Maintain Table T049B
OBAZ C FI Maintain Table FEDICUS
OBB0 C FI Maintain table T030 valuatn adj
OBB1 C FI Maintain Table T001G
OBB2 C FI Maintain Table TFMC
OBB3 C FI Maintain Table TFMC
OBB4 C FI Maintain Table TFMC
OBB5 C FI Maintain Table T001
OBB6 C FI Maintain Table TGSB
OBB7 C FI Maintain Table TGSB
OBB8 C FI Maintain Table T052
OBB9 C FI Maintain Table T052S
OBBA C FI Maintain Table T012C
OBBB C FI Maintain Table T012A
OBBC C FI Maintain Table T052 (Block Key)
OBBD C FI Maintain Table T045T
OBBE C FI Maintain Table T053R and T053S
OBBF C FI Maintain Table TCURD
OBBG C FI Maintain Table T005 (KALSM)
OBBH C FI Maintain Table T001Q (Document)
OBBI Maintain G/L Account Field Groups
OBBJ Maintain Sample Account Field Groups
OBBK C FI Maintain Table T055G (Banks)
OBBL C FI Maintain Table T055 (Banks)
OBBM C FI Maintain Table T055G (Docs)
OBBN C FI Maintain Table T055 (Docs)
OBBO C FI Maintain Table T010O
OBBP C FI Maintain Table T001 (OPVAR)
OBBQ C FI Maintain Table T044D
OBBR C FI Table T042R Maintenance
OBBS C FI Maintain Table TCURF
OBBT C FI Table T030 Maintenance GLU+GLU
OBBU C FI Maintain Table T044K List
OBBUSPRO Business Processes
OBBV C FI Maintain Table T030 BI2+SPACE
OBBW C FI Maintain Table T030 BI3+A00
OBBX C FI Maintain Table T030 BI4+SPACE
OBBY C FI Maintain Tables T028V + T028W
OBBZ C FI Subst. FI/0005: Activate
OBC1 C FI Maintain Table T054
OBC2 C FI Maintain Table T054A
OBC3 C FI Maintain Table TLSEP
OBC4 C FI Maintain Table T004V
OBC5 C FI Maintain Table T001
OBC6 C FI Maintain Table T001
OBC7 C FI Maintain Table T059Q
OBC8 C FI Table T001 Maintenance (TXKRS)
OBC9 External Group Number for Taxation
OBCA C FI Maintain Table T076B
OBCB C FI Maintain Table T076I
OBCC C FI Maintain Table T076K
OBCD C FI Maintain Table T076M
OBCE C FI Maintain Table T076S
OBCF C FI Maintain Table T007F
OBCG C FI Maintain Table T007K
OBCH C FI Maintain Table T007L
OBCI C FI Maintain Table T007I
OBCJ C FI Maintain Table T007J
OBCK FI Table Maintenance T001 (XSTDT)
OBCL FI Table Maint. T001 (MWSKV+MWSKA)
OBCM C FI Maintain Table T007F
OBCN C FI Maintain Table T007B
OBCO C FI Maintain Table TTXD
OBCP C FI Maintain Table TTXJ
OBCQ C FI Table T053G Maintenance
OBCR C FI Table T053V + T053W Maintenance
OBCS C FI Table T053E Maintenance
OBCT C FI Table T053A + T053B Maintenance
OBCU C FI Table T053C Maintenance
OBCV C FI FAKP: T021R with SL-AX
OBCW C FI table T053D maintenance
OBCX TTXC View
OBCY C FI Table TTYPV Maintenance
OBCZ C FI Maintain Table T021E
OBD1 Document parking posting date
OBD2 C FI Maintain Table T077D
OBD3 C FI Maintain Table T077K
OBD4 C FI Maintain Table T077S
OBD5 C FI Maintain Table T003B
OBD6 C FI Maintain Table TCURS
OBDA C FI Table T059E + T059G Maintenance
OBDB C FI Table T053R Maintenance
OBDC C FI Maintain View Cluster V_T060K
OBDD C FI Table T060K Maintenance
OBDE C FI Table T060M Maintenance
OBDF C FI Maint.view cluster V_T060o
OBDG C FI Maintain Table T076A
OBDH C FI Maintain Table T076E
OBDU Job Names for Data Transfers
OBE7 C FI Batch Input Customers
OBE8 C FI Generate Btch Input Rcrd Layout
OBEA Maintain Convertible Reports
OBEB Main.Table for Old Local Curr.(EURO)
OBEBGEN Electronic Banking: General
OBEBLADR Assign Banks to OFX partners
OBETX Number Assignment for Ext. Tax Docum
OBF1 C FI Maintain Table TFI01/TFI01T
OBF2 C FI Maintain Table TFI02
OBF3 Bank selection, current setting
OBF4 C FI maintain table T003
OBF5 C FI Maint. Table T042OFI/T042OFIT
OBF8 C FI Batch Input Vendors
OBFA C FI Corresp.Sort Variants/Corresp.
OBFB C FI Corresp.Sort Variants/Documents
OBFC C FI Corresp.Sort Variants/Lne Items
OBG1 C FI Maintain tbl T030 offsttng acct
OBG4 C FI Batch Input Documents
OBG5 C FI Batch Input G/L Accounts
OBG8 C FI Copy G/L Accounts Acc.To Ref.Ac
OBG9 C FI Maintain Table TSAKR
OBGA C FI G/L Account With Ref.: Display
OBH1 C FI Doc.No.Range: Copy Company Code
OBH2 C FI Doc.No.Range: Copy Fiscal year
OBIA C FI Maintain View Cluster VC_TFAG
OBIB Parameter Transaction for V_TFAGM
OBJ1 C FI Year End Financial Statement
OBJ2 C FI Year End Compact Doc.Journal
OBJ3 C FI Year End Bill of Exchange List
OBJ4 C FI Year End G/L Account Balances
OBJ5 C FI Year End G/L Account List
OBJ6 Posting Totals
OBJ7 Bill of Exchange Charges Statement
OBK1 C FI Year End OI Customer List
OBK2 C FI Year End Customer Acct Balances
OBK3 C FI Year End Customer List
OBK4 C FI Year End OI Vendor List
OBK5 C FI Year End Vendor Acct Balances
OBK6 C FI Year End Vendor List
OBK7 Subledger Accts Bal.Carried Forward
OBK8 G/L Accounts Balance Carried Forward
OBK9 Payment Notices Correspondence
OBKA Account Statement Correspondence
OBKB Internal Documents Correspondence
OBKC Individual Letters Correspondence
OBKD Document Statements Correspondence
OBKE Customer Stmnt Corresp.Account Stmnt
OBKF Failed Payment Correspondence
OBKG Correspondence Sel.Criteria Letters
OBKR Maintain Number Range: FI_RECEIPT
OBKS C FI Table T058A Maintenance
OBKT C FI Table T058B Maintenance
OBKU C FI Table T011A + T011B Maintenance
OBKV C FI Table T011E + T011F Maintenance
OBKW C FI Table T011V Maintenance
OBL1 Consistency Check: Auto.Pstg (Docu.)
OBL2 Consistency Check: Auto.Pstg (ErAny)
OBL3 Consistency Check: Sp.G/L (Docu.)
OBL4 Consistency Check: Sp.G/L (Err.Anly)
OBL5 Consistency Check: Pmnt Prog.Config.
OBL6 Consistency Check: Dunn.Prog.Config.
OBM1 C FI Month End Advance Tax Return
OBM2 C FI Month End Financial Statement
OBM3 C FI Month End Foreign Trade Regns
OBM4 C FI Month End Compact Doc.Journal
OBM5 C FI G/L Balances Monthly Report
OBM6 Posting Data Reconciliation
OBMD C FI Selec.Variants Dunning/Dun.line
OBMK C FI Selec.Variants Dunning/Dunn.hdr
OBN1 C FI Month End OI Customer List
OBN2 C FI Month End Financial Statement
OBN3 C FI Month End OI Vendor List
OBN4 C FI Month End Vendor Acct Balances
OBNB Transaction Code for SAPMFKM2
OBO1 C FI FAKP Line Item Line Layout
OBO2 C FI FAKP Credit Mangmnt Line Layout
OBOB C FI FAKP Line Item Line Layout
OBOFXBUS OFX: Business Customizing
OBOFXTECH OFX: Technical Customizing
OBP1 C FI create distribution key
OBP2 C FI Change Distribution Keys
OBP3 C FI display distribution key
OBP4 C FI delete distribution key
OBP5 Delete FI planning data
OBP6 G/L: Versions
OBPL Subsequently post CO plan.data to GL
OBQ1 C FI Condition Compnt: Condit.Types
OBQ2 C FI Condit.Component: Access Seque.
OBQ3 C FI Condition Component: Calc.Proc.
OBR1 Delete Documents
OBR2 Delete Subledger Accounts
OBR3 C FI Maintain Table T001
OBR4 Delete Banks
OBR7 Maintain account type life
OBR8 Maintain document type life
OBRD Customers: maintain report selection
OBRK Vendors: maintain report selection
OBRS G/L: maintain report selection
OBRX Flexible G/L: Maintain Report Selec.
OBS1 C FI Create Ledger
OBS2 C FI Change Ledger
OBS3 C FI Display Ledger
OBS4 C FI Delete Ledger
OBT1 C FI Maintain Table TTXID (KNA1)
OBT2 C FI Maintain Table TTXID (KNB1)
OBT3 C FI Maintain Table TTXID (KNKK)
OBT4 C FI Maintain Table TTXID (LFA1)
OBT5 C FI Maintain Table TTXID (LFB1)
OBT6 C FI Maintain Table TTXID (SKA1)
OBT7 C FI Maintain Table TTXID (SKB1)
OBT8 C FI Maintain Table TTXID (BELEG)
OBT9 C FI Maintain Table TTXID (MR01)
OBU1 Document Type/Posting Key Options
OBUV TxApportnmnt for Cross-Co.Cde Trans.
OBV1 C FI Int.For Dys Overdue Acct Deter.
OBV2 C FI G/L Acct Bal.Int.Calc.Acct Det.
OBV3 C FI Cust.Bal.Int.Calc.Acct Determ.
OBV4 C FI Vend.Bal.Int.Calc.Acct Determ.
OBV5 C FI Maintain Table T030Q
OBV6 C FI Maintain Table T030V
OBV7 C FI Maintain Table T001O
OBV9 C FI Act Det.Vendor Intrst on Arrs
OBVS C FI Display View
OBVT C FI Display Restricted View
OBVU C FI Maintain View
OBVV C FI Maintain Restricted View
OBVW C FI maintain view
OBVY C FI Maintain Table T030H
OBW1 C FI Maintain Table T001F
OBW2 C FI Maintain Table T001G
OBW3 Instructions in Payment Transactions
OBWA C FI Table VBWF01+VBWF02 Maintenance
OBWB C FI Table VBWF08 Maintenance
OBWC C FI Table VBWF03 Maintenance
OBWD C FI Table VBWF05 Maintenance
OBWE C FI Table VBWF06+VBWF07 Maintenance
OBWF C FI Table VBWF09+VBWF10 Maintenance
OBWG C FI Table VBWF04 Maintenance (Cust)
OBWH C FI Table VBWF04 Maintenance (Vend)
OBWI C FI Table VBWF04 Maintenance (G/L)
OBWJ C FI Table T001 Maintenance (WFVAR)
OBWK C FI Table VBWF04 (Assets)
OBWL C FI Maintain Tables VBWF11 + VBWF12
OBWM Organizational objects full release
OBWO C FI Withholding Tax
OBWP Payment release by authorized person
OBWQ Payment Release Document Types
OBWR C FI Maintain Table FEDIWF1
OBWS C FI Withholding Tax
OBWU C FI Withholding Tax
OBWW C FI Withholding Tax
OBWZ Number Range Maintenance: WITH_CTNO
OBX1 C FI Table T030B: G/L Acct Posting
OBXA C FI Table T030
OBXB C FI Table T030
OBXC C FI Table T030
OBXD C FI Maintain Table T030
OBXE C FI Table T030
OBXF C FI Sort Bank Directory
OBXG C FI Maintain Bank Direc.Automatic.
OBXH C FI Table T041A/T041T
OBXI C FI Table T030
OBXJ C FI Table T030B
OBXK C FI Table T030
OBXL C FI Table T030
OBXM C FI Table T030
OBXN C FI Table T030 GAU/GA0
OBXO C FI Table T030 KDW
OBXP C FI Maintain Table T030 zaf
OBXQ C FI Table T030 KDZ
OBXR C FI Table T074
OBXS C FI Table T030
OBXT C FI Table T074
OBXU C FI Table T030
OBXV C FI Table T030
OBXW C FI Table T030B Cleared Invoices
OBXY C FI Table T074
OBXZ C FI Table T030 G/L Accont Clearing
OBY0 C FI Copy CoCde with Ctry Chrt/Accts
OBY2 C FI Copy company code (G/L account)
OBY6 C FI Maintain Table T001
OBY7 C FI Copy Chart of Accounts
OBY8 C FI Delete Chart of Accounts
OBY9 C FI Transport Chart of Accounts
OBYA C FI Table T030
OBYB Maintain automatic postings accounts
OBYC C FI Table T030
OBYD C FI Table T030
OBYE C FI Table T030
OBYF Revenue Account Determination
OBYG C FI Table T030
OBYH C FI Table T030
OBYK C FI Table T045W
OBYL C FI Table T030 HRI + HRC
OBYM C FI Table T074 Bill of Exchange
OBYN C FI Table T074 Bill Receivable
OBYP C FI Table T074 Check/Bill of Exch.
OBYR C FI Table T074
OBYS C FI Table T074 Tangible Fixed Asset
OBYT C FI Table T030 HRI + HRD
OBYU C FI Table T030 HRI + HRD
OBYY C FI Table T030 Maintenance KDT/KDT
OBYZ C FI Condition Components
OBZ1 C FI FBZP T042B
OBZ2 C FI FBZP T042
OBZ3 C FI FBZP T042Z
OBZ4 C FI FBZP T042E
OBZ5 C FI FBZP T042A
OBZ6 C FI FBZP Consistency Check
OBZ7 C FI Users
OBZ8 C FI Profiles
OBZ9 C FI Authorizations
OBZA Reporting Selection: Global Menu
OBZB Reporting Selection: Accts Receivble
OBZC Reporting Selection: Accts Payable
OBZD Reporting Selection: G/L Accounts
OBZE Reporting Selection: Documents
OBZF Reporting Selection: Documents
OBZG Reporting Selection: G/L Accounts
OBZH C FI Maintenance Table TCCFI
OBZI C FI Maintenance Table TCCAA
OBZJ C FI Maintenance Table T000CM
OBZK C FI Maintenance Table T001CM
OBZL C FI Maintain Table T001 (XCOS)
OBZM C FI Substitution FI/0005: Create
OBZN C FI Substitution FI/0005: Change
OBZO Doc.Types for Single Scrn Transactns
OBZT Single Screen Transaction Tax Code
OBZZ
OB_7 C FI Maint.Table T044G Val.Adj.Key
OB_8 C FI Maintain Table T044I Base Value
OB_9 C FI Maintain Table T044J: Display
OB_GLACC01 Create G/L accounts with reference
OB_GLACC02 Create G/L accounts with reference
OB_GLACC11 G/L acct record: Mass maintenance 01
OB_GLACC12 G/L acct record: Mass maintenance 02
OB_GLACC13 G/L acct record: Mass maintenance 03
OB_GLACC21 Configuration G/L account record
OB_T001_CESSION FI Customizing: Accts Rble Factoring
OB_V_CESSION FI Customizing: Accts Rble Fact.Ind.
Hi all
Can any tell me
If I post an transaction in F-02, what are all the tables will be affected by that transaction.
Thank you
Mahesh.J
[email protected]FSKB G/L Account Posting
this transaction is not working -
Adding customer field to selection screen of RFKORD11 - Customer Statement Printing Program:
Hello,
We are required to add an important customer field to selection screen of customer
statement printing program: RFKORD11 for our South African branch.
Please advise us regarding this matter,
is there a proper user-exit or a repair is needed?
Kind Regards.Enhancement
text
F050S001
FIDCMT, FIDCC1,
FIDCC2: Edit user-defined IDoc segment
F050S002
FIDCC1: Change
IDoc/do not send
F050S003
FIDCC2: Change
IDoc/do not send
F050S004
FIDCMT, FIDCC1,
FIDCC2: Change outbound IDoc/do not send
F050S005
FIDCMT, FIDCC1,
FIDCC2 Inbound IDoc: Change FI document
F050S006
FI Outgoing IDoc:
Reset Clearing in FI Document
F050S007
FIDCCH Outbound:
Influence on IDoc for Document Change
F180A001
Balance Sheet
Adjustment
FARC0001
Enhancements within
archiving (FI)
FARC0002
Additional Checks for
Archiving MM Vendor Master Data
FEDI0001
Function exits for
EDI in FI
FICT0001
Exits for
inter-company transactions
RFAVIS01
Customer Exit for
Changing Payment Advice Segment Text
RFBVX001
Enhancement for bank
directory transfer (Austria)
RFEPOS00
Line item display:
Checking of selection conditions
SAPLBANK
User exit: Bank data
SAPLF040
WF: Preliminary
posting (authorized for release)
SAPLF051
Workflow for FI
(pre-capture, release for payment)
SAPLFCPD
One-time account data
or different payee in booking
SAPLSSRV
User exit: Bank
account numbers
RFKORIEX
Automatic
correspondence
please check which one is better . -
FBV1 - missing standard field and adding customer field
Hi there,
I am in a process of developing a batch input program based on RFBIBL00 to upload preliminary posted documents.
The problem is some fields are not there. A standard field BKPF-REINDAT is missing. Also there is a requirement to add a customer field from BSEG (on vendor screen).
I have searched SAP notes for possible solutions, most of them include modifying screens by hand and adding the required fields there (i.e. Note 1347046 - VATDATE: Field missing in batch input parking (FBV1)).
This is quite a serious modification, requiring access key to change SAP objects. Before I decide to change SAP standard objects I kindly ask whether anyone tried that ? REINDAT might work, as it's a standard field, but I'm note sure about customer fields.
Has anyone tried modifying FBV1 or any of FI posting screens by hand and can provide some input on this ?
Thanks,
BartDear Bart ,
as You know the field in question is intended only for US-Federal customers.
The field is not availble into the standard system using the parking transaction; therefore You should run se51 at Your own responsability and do the changes.
If You need to be completely sure about the impact on the customer System, please kindly open a message on the marketplace.
I hope this can help.
Mauri -
Trigger workflow for MIRO invoice creation
Hello,
In standard functionning it is not possible to trigger the workflow for documents coming from MM.
When using transaction MIRO and selecting invoice creation the created document has following value :
BKPF-AWTYP = 'RMRP'. whereas creating it from FB60 results to BKPF-AWTYP = 'BKPF'.
The problem is standard code checks AWTYP is not equal to 'RMRP' before creating event to start the standard workflow for invoice validation.
Question : why sap doesn't allow workflow creation for invoices from MIRO?
Thanks for your answers.
Best regards,
Laurent.Hi,
here they are...
WS20000397 MMIVBlockedP Treatment of inv. blkd for price, Log.IV
WS20001004 MMIVToRel Release the Completed Log. IV Document
WS00400026 MMIVquantity Treatment inv.blocked f.quantity reasons
WS20001003 MMIVToCompl Complete the Parked Log. IV Document
WS00400027 MMIVprice Treatment invoic.blocked f.price reasons
All of these workflows are a one-step / one-level of approval and needs some workflow configuration at least for the agent assignments. For a full-blown workflow you should take these workflows as an example, how you could work with it.
The last two workflows work with preliminary posting on the miro (transaction MIR7).
Best regards,
Florin -
give me the mm related standard tables
Description Table Name
Material Cost Distribution MAKV/MAKG/MAKZ
Other Related EMARA
Structure EMARC
MRP Related EMARC1
Purchase Related EMARC2
PPC Related EMARC3
Material Export Control MAPE/MAEX
Materials --> Task List MAPL
General Data MARA
C Segment MARC
Storage Location /Batch Seg. MARD
Unit of measure MARM/MAMT
Material Control record MARV
Material to BOM Link MAST
Material Valuation MBEW
Stock at Production Storage Bin MBPR
Material Document MSEG
Sales Order Stock MSKA
Special Stocks with Customer MSKU
Project Stock MSPR
Material Master status MSTA
General Data LFA1
VAT Details LFAS
Company Code LFB1
Dunning Details LFB5
Bank Details LFBK
Transactions Details LFC1
Ex/Im Related Details LFE1
Supplying Region LFLR
Purchase Organisation LFM1
Purchasing Data LFM2
Partner Functions WYT3
Stocks MSLB
Vendor Evaluation - Header ELBK
Vendor Evaluation - Material related ELBM
Vendor Evaluation - Main criterion ELBP
Basic Data ASMD
Service Short texts ASMDT
General Data EINA
Purchase Organisation Data EINE
Order Price History EIPA
Ex/Im Header Data EIKP
Ex/Im Detail Data EIPO
Purchasing Source lists EORD
General Data KOMG
Conditions (Item) KONP
General Data AEBAN
Requisitions EBAN
I/O for purchase req. RM06E
Purchasing Docu. Header EKKO
Purchasing Docu. Item EKPO
Conditions in PO KONV
Scheduling Agreement Release Documentation EKEH
Header Data for Scheduling Agreement Releases EKEK
Order Acceptance/Fulfillment Confirmations EKES
Delivery Schedules EKET
Partner Roles EKPA
Quota file header EQUK
Quota file item EQUP
Purchasing Docu. Item EKPO
Release Documentation EKAB
Vendor Address EKAN
History of Purchasing Document EKBE/EKBZ
Purchasing Condition EKKI
Account Assignment EKKN
Shipping Specifications EKPV
Order Acceptance/Fulfillment Confirmations (Shipping documents) EKES
ERS Procedure EKRS
Reservation/dependent requirements RESB
Document Header: Reservation RKPF
CLASS HEADER DATA KLAH
Class Type Texts TCLAT
Characteristics of a Class KSML
Characteristic CABN
Characteristic values CAWN
Value Texts CAWNT
Allocation Table: Object to Class KSSK
Object to Characteristic Values AUSP
Material master valuation info if split valuation is used
MBEW
Batch master MCHA
Storage location batches quantities if batch mgmt is cross plant MCH1
Storage location batches quantities if batch mgmt is not cross plant MCHB
Stocks with vendor (includes batch level) MSLB
Stocks against Sales orders ENT5117
ENT5117 comprises MARD, MSKA
Confirmation control keys T163E
Customising - Description of confirmation control keys T163F
Customising - Link between confirmation control key and confirmation T163G
Confirmation control keys description T163M
Confirmations table for purchase orders EKES
PO line item details -confirmation control key for a PO line item EKPO
Incoterms General TINC/TINT
A/C entries BSIM
Against Orders AUFM
Purchase Order CEKKO
Purchase Requisition CEBAN
Preliminary posting doc.segment for vendors VBSEGK
Preliminary posting doc.segment for G/L accts VBSEGS
Parked invoices have an entry in the BKPF table but do not have an entry in the BSEG table until they are actually posted In the VBSEGS table, all the material line items for a parked invoice are stored. When the parked document is actually posted, the entry from this table is deleted and an entry is made in the MSEG table as a final posting.
Storage Bins LAGP
Control Cycle Header PKHD
Storage Unit Header Records LEIN
Transfer Req. Header LTBK
Physical Inventory Document - Header IKPF
Physical Inventory Document Items ISEG
Physical Inventory Conversion Parameter Appendix ISEGO1
Physical Inventory Document Additional Quantities Appendix ISEGO2
LIFO Material Layer MYML
LIFO Period Stocks, Individual Material MYMP
LIFO-relevant materials MYMS
LIFo Pool Layer MYPL
Forecast Values PROW
Quality notification QMFE
Quality notification - items QMEL
Inspection lot record QALS
Inspection processing: Usage decision QAVE
Material and inspection link QMAT
Problems: Vendor Analysis S102
Problems: Material Analysis S102
Sales Related material data S004
Purchasing group related data S011
Purchasing related LIS reports S012
Vendor Evaluation data S013
Subsequent Settlement S015
Material Usage S026
Stocks related LIS reports S031
Current Stock & grouping terms S032
Movements for single records S033
Movements for Batches S034
Batch Stocks S035
Batch Analysis data S038
Planning S039
Vendor Statistics S068
Purchasing S080/S081/S082
Stock placements/Removals WM S090
Flow of Quantities S091
Stock/Requirements Analysis S094
LIS Related Views MCDY/MCL
Client T000
Account Assignments T163K/T163I
Authorization Objects TOBJ/TOBJC/TOBJT
Certificate Catg T069
Check Table Info. DD08L
Control Table for Vendor Evaluation T147
Currency Codes TCURC
Definition for Main Criteria for Vendor Evaluation T147A
Definition for Subcriteria for Vendor Evaluation T147C
Definition of Evaluation Paths T77AW
Definition of Scope of List: Vendor Evaluation T147M
Description of Evaluation Groups T087T
Description of Weighting Keys in Vendor Evaluation T147F
Descriptions of LIS Information Structures TMC4T
Descriptions of Logical Screens T133B
Descriptions of Material Status from MM/PP View T141T
Descriptions of Release Groups T16FH
Descriptions of Release Indicators for Services T16FM
Descriptions of Release Indicators: Purchasing Documents T16FE
Descriptions of Release Strategies T16FT
Division Master TSPA
Domain Names DD01L
Domain Range DD07L
Field Names DD04L
Inv. Management: Text Table for Trans./Event Types Allowed T158T
Inv. Managmt Print Function: Active Form Version, Labels T159M
Inv. Mngmt - General: Transaction/Event Types Allowed T158V
Inv. Mngmt Print Function: Maintain Text Name for Labels T159O
LIS - Environment generation sample reports and references TMCE
LIS Default Sets and Format Classes TMCSE
LIS Evaluations TMCSA
LIS Evaluations: Texts TMCST
LIS Information Structures TMCSB
LIS Libraries TMCSC
LIS objects TMCO
LIS Planning: Key Matrix Selection Control Table T444P
LIS Planning: Screen Sequence Control Table T444K
LIS Readings for Internal Number Assignment: Alphanumeric TMCSD
LIS Standard Reports/Layouts for Evaluations TMCSF
LIS Standard Reports/Layouts for Evaluations: Texts TMCSG
LIS Transaction Code Control TMCTC
LIS: Characteristic Texts (external data and R/2) TMCTX
LIS: Status Management - Updating TMC2
Logon data USR02
Main Criteria in Vendor Evaluation T147G
Material authorization groups in quality management TQ01B
Material Group T023
Material Group Descriptions T023T
Material Groups T023
Material Ledger Table TCKM1
Material Ledger Text Table TCKMT
Material master field selection T130A
Material master screen sequence control T138B
Material Pricing Group 1 TVM1
Material pricing group 1: Description TVM1T
Material Pricing Group 2 TVM2
Material Pricing Group 2: Description TVM2T
Material Pricing Group 3 TVM3
Material pricing group 3: Description TVM3T
Material Pricing Group 4 TVM4
Material pricing group 4: Description TVM4T
Material Pricing Group 5 TVM5
Material pricing group 5: Description TVM5T
Material Pricing Group for Export/Import: Descriptions TVFMT
Material Pricing Group: Shipping Materials TVEGR
Material Pricing Group: Shipping Materials: Designations TVEGRT
Material statistics groups TVSM
Material Status from Materials Management/PPC View T141
Material Substitution: Reasons TVSU
Material Substitution: Texts for Reasons TVSUT
Material Taxes TSKM
Material Type Descriptions T134T
Material Types T134
Material Types Allowed in BOM T415M
Material: Account Assignment Group Texts TVKMT
Material: MRP profiles (definition) T401A
Materials Provided Indicator Texts T417T
Materials Provided Indicators T417
Materials: Account Assignment Groups TVKM
Materials: Item Category Groups in Mat.Master: Texts TPTMT
Materials: Item Category Groups in Material Master TPTM
Materials: Product Hierarchies T179
Materials: Product hierarchies (inverse) T179I
Materials: Product hierarchies: Texts T179T
Materials: Sales status TVMS
Materials: SD Status: Texts TVMST
Materials: Statistics groups: Texts TVSMT
Movement Type T156
Movement Type Text T156T
Movement Type: Quantities/Value Posting T156S
Movement Types: Screen Selection T156B
MRP T024D
MRP default values per material type TMW00
MRP description T438T
MRP distribution key (texts) T437W
MRP group text T438X
MRP lot sizes T439A
MRP Profile Descriptions T401T
MRP transaction control T450
MRP Type T438A
Physical Inventory Stock Types T064A
Physical Inventory Stock Types and Allocated Movement Types T150
Physical Inventory: Texts T064T
PO Tolerance Limits T169G
Pricing Procedure T683
Pricing Procedure: Data T683S
Pricing Procedures: Determination in Sales Docs. T683V
Pricing Procedures: Procedure: Texts TVKVT
Pricing Procedures: Texts T683T
Pricing Procedures: Transaction TVKV
Purchase Order History Categories T163B
Purchasing Area T026
Purchasing Document Types T161
Purchasing Group T024
Purchasing Groups T024
Purchasing organisations T024E
Purchasing Organizations T024E
Purchasing Organizations T024Z
Purchasing value key T405
Purchasing Various Control Parameters TMED
R/3 Objects TADIR/TRDIR
Release Codes T161E
Release Codes T16FC
Release Groups T16FG
Release Indicator, Purchase Requisition T161S
Release Indicators: Purchasing Document T16FB
Release Indicators: Service Entry Sheet T16FL
Release Point Assignment for Purchase Requisition Release T161F
Release Prerequisite, Purchase Requisition T161G
Release Prerequisites T16FV
Release Statuses T16FK
Release Strategies T16FS
SAP Tables DD02L
Scope of List: Vendor Evaluation T147O
SQL Tables DD06L
Stock display: basic list/detail list T136
Stock Mngmt Levels for Inventory Sampling T064S
Stock Types and Allocated Fields in Physical Inventory T150F
Stock Types and Texts for Physical Inventory T064B
Stock Types and Their Values T156C
Storage Bin Structure for Automatic Creation of Storage Bins T343
Storage Bin Type Search T334P
Storage Classes T646L
Storage Classes Allowed per Storage Type T331L
Storage Condition Texts T142T
Storage Conditions for Materials T142
Storage for Search Terms TSFST
Storage Locations T001L
Storage Section Indicators T304
Storage Section Names T302T
Storage Section Search T334B
Storage Type Control T331
Storage Type Control for Block Storage T331B
Storage Type Descriptions T301T
Storage Type Indicators T305
Storage Type Search T334T
Storage Unit Type Check T334E
Storage Unit Types T307
Table + Field Name DD03L
Table Tech. Specs DD09L
Table/Field Def. DD03VV
Texts for Main Criteria in Vendor Evaluation T147B
Texts for Scope of List in Vendor Evaluation T147N
Texts for Subcriteria in Vendor Evaluation T147D
Transaction Code Texts TSTCT
Transaction Codes T588A
Transaction Control: Inventory Management T158
Transaction Control: Physical Inventory T158I
Transaction Control: Services Management T265
Transaction Description T167T
Transaction Parameters T7032
Transaction Texts: Invoice Verification T169X
Units of Measure T006
User address data USR03
User master record USR01
Valuation - Control TKEVA01
Valuation acc. to Length of Absence T5A4T
Valuation area T001K
Valuation area control table TCKM2
Valuation Category/Valuation type T149B
Valuation Class Descriptions T025T
Valuation Classes T025
Valuation Classes T025
Valuation Classes T554O
Valuation difference temporary storage TBKOW
Valuation Levels for LIFO Inventory Valuation T001Y
Valuation method names T044B
Valuation methods T880B
Valuation of Pay Scales for Statistics T5D3N
Valuation Strategies (CO-PA) TKEVA02
Valuation type/valuation class T149
Valuation types for valuation area T149A
Valuation variant for order costing TCO10
Valuation Variants in Costing TCK05
Valuation Variants in Costing - Texts TCK06
Valuations T863W
Vendor account groups T077K
Vendor Evaluation: Assignment Percentages - Points Scores T147K
Vendor Hierarchy Category TLHIT
Vendor master data screen selection (purch.org.) T079M
Warehouse costs for MRP lot size T439L
Warehouse Number Descriptions T300T
Weighting Keys in Vendor Evaluation T147J
WM Default Values T340D
WM Movement Types T333
WM Names of Storage Bin Types T303T
WM Screen Selection T341
WM Storage Bin Types T303
WM Storage Sections T302
WM Storage Types T301
WM Transactions T340
WM Warehouse Numbers T300
WM: Assignment MM Storage Location to WM Warehouse Number T320 -
Adding additional field 1 to selection screen of CATSSHOW (CADO)
Hello all,
We recently added one of the additional field's to show up on the data entry section when using
transaction CAT2...This is working fine and the data is entered into CATSDB.
When using CADO, one can display the addtional field 1 and sort by this field.
However, the users now want this additional field1 to be one of the selections when they
use report CATSSHOW (CADO).
Is there some type of way to configure SAP to have one of these additional fields show up
as a selection field on program CATSSHOW (CADO)? My searches in this forum and the web
have not shown me a solution yet.
Or do I have to create a 'Z' version of CATSSHOW like ZCATSSHOW and do this myself?
Thank-you,
Rick CrawfordEnhancement
text
F050S001
FIDCMT, FIDCC1,
FIDCC2: Edit user-defined IDoc segment
F050S002
FIDCC1: Change
IDoc/do not send
F050S003
FIDCC2: Change
IDoc/do not send
F050S004
FIDCMT, FIDCC1,
FIDCC2: Change outbound IDoc/do not send
F050S005
FIDCMT, FIDCC1,
FIDCC2 Inbound IDoc: Change FI document
F050S006
FI Outgoing IDoc:
Reset Clearing in FI Document
F050S007
FIDCCH Outbound:
Influence on IDoc for Document Change
F180A001
Balance Sheet
Adjustment
FARC0001
Enhancements within
archiving (FI)
FARC0002
Additional Checks for
Archiving MM Vendor Master Data
FEDI0001
Function exits for
EDI in FI
FICT0001
Exits for
inter-company transactions
RFAVIS01
Customer Exit for
Changing Payment Advice Segment Text
RFBVX001
Enhancement for bank
directory transfer (Austria)
RFEPOS00
Line item display:
Checking of selection conditions
SAPLBANK
User exit: Bank data
SAPLF040
WF: Preliminary
posting (authorized for release)
SAPLF051
Workflow for FI
(pre-capture, release for payment)
SAPLFCPD
One-time account data
or different payee in booking
SAPLSSRV
User exit: Bank
account numbers
RFKORIEX
Automatic
correspondence
please check which one is better . -
How to fix the above mentioned, *"special Incoming Closed margins"*.
Valuation runs (TPM1) fails with the error below:
Unfixed bus. trans. with posting date 02/23/2012 before key date (long text)
Message no. TPM_TLV1028
Diagnosis
The position that is to be valued contains a position-relevant business transaction Close margin listed options and futures in status Scheduled with posting date 02/23/2012 This is earlier than the valuation key date.
Question is how to fix the above mentioned, "special Incoming Closed margins".
PLease note that TPM18 or TBB1 does not work....
Regards,
RahulHello Lorenz,
I get no flows selected but report tpm13 clearly shows there is an OUTGOING CLOSED MARGIN update type in scheduled status ?
Any ideas. This issue has been reported before but no results.
Regards,
Rahul
Maybe you are looking for
-
Question on App Process and Java script performance
I have quick question regarding performance of Application process and Javascript. I'm having OnDemand Application process, which fetches data from db and thru javascript in page, i'm invoking the application process. My question is : If I did not re
-
I want to partition my drive. help?
hey all i'm thinking about partitioning my drive. i want to do it because i am a pro tools user and i want to install 2 different versions of pro tools on my computer to test any newer releases on one and work with a more stable version on the other.
-
Dynamic Parameter Problem after Upgrade to 2008 from XI
Post Author: phpsmitty CA Forum: Crystal Reports I'm having a problem with a dynamic populated parameter options on a report. I open the report up in XI (where the report was developed) and it works as expected. If I open up the same report up in 200
-
Audigy 2 ZS & Gigaworks S750 & Sat Receiver Toslink Connect
Not sure if this is a noob question or not, but can I connect the Toslink (optical) connection on my satellite receiver directly to my Audigy 2 ZS card via Toslink to Mini cable? I assume it would just plug into the "Line In" mini jack? And if so, wi
-
Trying to install PSE13. File archive missing?
The error message is: "The file archive part of Adobe PSE13 is missing. You need all parts in the same folder..." How do I put all parts into the same folder?