Subledger posting in Derived Business Transactions

Hi,
In TPM18 - derived business transaction, is it possible to post in subledger? example, unrealized forex gain will have the following posting;
01 - Loan Payable (customer subledger)
50 - Unrealized Forex Gain
Thanks,
Chaikaru

Hi,
I am having certain doubts in your accounting entry. Shouldn't you post a corresponding entry as part of valuation. Could you please explain the business logic in using unrealized gain account for posting in derived business transactions because it should be a realized gain.
Also why do you want to map to the subledger level? In case if you have a loan managed at the customer level, then also you would account for the loss/gain at the position account only.
I strongly doubt whether such a requirement can be met. May be you can try changing the position specifications for your derived update type, but still not sure whether it will pick the customer subledger.
Regards,
Ravi

Similar Messages

Posting of Derived Business transactions

Dear SAP Gurus
Recently I had a requirement wherein the DBT was to be posted to SL. I found that DBT posting is not possible to SL and the system gave me an error message that the "amount is not available in payment currency"
The question is when the system allows a normal flow to be posted to SL in payment currency why not in case of Derived Business Transaction. Is there a workaround available
Any help would be appreciated.
Regards
Virendra Malik

Hi
You have rightly said that DBT is meant for internal posting and ideally must be posted to a GL only. However I have this special requirement when I want to do the posting through DBT for update type DBT_E002 (Translation of Negative Purchase Value). In this case I do not want to do the SL posting of foreign currency repayment which is represented by the the main flow (update type MM1130-). This main flow update type has the net amount of two transactions DBT_E002 (Translation of Negative Purchase Value) and DBT_B006 (Forex Gain (planned outflow)). I want the SL posting to be done of the amount being shown in DBT_E002 and Gl posting for the amount being shown in DBT_B006.
Hope the above clarifies.
Regards
Virendra Malik

Derived business transactions and TBB1

Dear experts,
My question concerns Money Market derived business transactions.
When I enter position outflows that are not transfer postings, the system generates derived translations that update the position components (proportionate reduction) u2013 DBT_E001/DBT_E002.
These translations are not relevant for posting, but have a status Planned.
The question: is it possible to fix these derived flows during posting of operative business transactions in TBB1?
Right now I can fix them only through TPM18, which is very inconvenient to run separately.
Any help would be appreciated.
Best wishes,
Irina

Hi,
In status control the setting is status of plan and hence the derived transactions will always be generated in planned status and you have to fix them through TPM18.
In order to post it through TBB1 itself, the control setting should have same status option. But check with the business also whether this is not going to have any other effect because this is at the central company code and valuation area level. All derived transactions will have the same status of the operative transactions itself.
Regards,
Ravi

RKP3 Business Transactions

Does anyone know which tcode posts values using business transaction RKP3 to WBS elements? I see secondary costs posted against a WBS element, but can't seem to find the transaction that posted it. I would like to say it is CJ40 - activity input, but I can't go into that screen in my production system, so I am assuming that it could be some other transaction.
What I am trying to get to is someone loaded some cost during data migration, and it appears as if they used an activity type with rate $1, because COSS table shows Quantity as 5000 units, where the cost is $5000 as well. This is causing some of my reports to be showing ridiculous numbers for plan hours on the project.
Any ideas?

I figured this thing out. It's basically coming from activity input for WBS (CJ40). The planning profile had to be complete.

IO Allowed Business Transaction FI Posting

Dear All,
I am trying to add business transaction FI Posting allowed for the order, can you please guide me where and how I can add that, currently it is showing in red.
I tried through KO02, it is not allowing to add any new business transaction
Thanks in advance for your quick response
Thanks
Prakash

Hi,
Firstly Release the Internal order as explained above.
In case, it is still not allowing FI postings, look at the User defined Status and check whether the existing status is allowing the FI postings are not. If not change the status to another status which allows the FI postings.
Thanks
Siva

Business transaction events in FI document posting

Dear All
Has anyone worked with business transaction events in FI document posting.
Function module <b>SAMPLE_PROCESS_00001150</b>
Please send me the code and i will modify according to my requirement.
Anyone help is highly appreciated.
Thanks in advance
Thanks
Sonali

Hi,
Check this link for step by step process to implement BTE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
Thanks,
Naren

Business transaction key in account determination..?

Hi all
Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
Pls giv me expaination,
Reply will be rewardable..
Thanks
sap-mm

Hi MM,
Please Search in SDN threads solution is given already in lot of threads.
Go to SAP Library
SPRO> Help> SAP Library
Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
Click on IMG ACTIVITY DOCUMENTATION
These transactions are important for Accounts.
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
Agency business: income (AG1)
This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
Agency business: expense (AG3)
This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
Del credere (DEL)
Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange Rate Differences Materials Management(AVR) (KDG)
When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
Exchange Rate Differences from Lower Levels (KDV)
In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
Accruals and deferrals account (material ledger) (LKW)
If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
Price Difference from Exploded WIP (Lar.) (PRA)
If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
Differences (AVR Price) (PRC)
In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Price Differences (Material Ledger, AVR) (PRG)
When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
Price differences in cost object hierarchies (PRK)
In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
Price Difference from Exploded WIP (Mat.) (PRM)
If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
Price differences, product cost collector (PRP)
During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Offsetting entry: price differences, product cost collector (PRQ)
The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Price Differences from Lower Levels (PRV)
In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
Price differences for material ledger (PRY)
In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
Expense and revenue from revaluation (retroactive pricing, RAP)
This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
Invoice reductions in Logistics Invoice Verification (RKA)
This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Inflation posting (WGB)
Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
WIP from Price Differences (Internal Activity) (WPA)
When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
WIP from Price Differences (Material) (WPM)
When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
GR/IR clearing for material ledger (WRY)
This transaction/event key is not used from Release 4.0 onwards.
Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
Reg,
Ashok
assign points if useful.

Doubt about "Business Transaction"

Hello Experts,
On the transaction KE4G, we assign "Business Transaction" to "Characteristic Group". Here goes my question, where does this field "Business Transaction" comes from? it belongs to FI, CO, SD ?? is it a customizable field? a standard one?
Thanks in advance!
Regards.
leandro

Hi,
business transaction is a SAP internal information for each posting, its not customizeable. Based on the source transaction it is added to every line item.
SAP F1 help for this field:
More than one business transaction can be executed in a system
transaction. One business transaction may also be executed in multiple
system transactions.
best regards, Christian

Business Transaction Control is not Working for Equipment Status.

Hi All,
I have created a Status Profile for Equipment / Functional Location & assigned 5 Status under this Profile i.e. NEW, COM (Commissioning), INS(Inservice), CAM (Care & Maintenance) & DCM (De Commissioned). For Status DCM i have assigned Transaction control FORBIDDEN for "Enter PM processing data , Enter PM planing data & Create Meas. Doc."activities.
It Means, whenever user creates Plant Maintenance Order OR Notification, Maintenance Plan OR Maintenance Item & Measurement Document for any Equipment / FL having this user status (DCM), system should not allow creation of above mentioned object.
In my scenario, system is giving an standard error message " The business transaction cannot be carried out" during creation of "Plant Maintenance Order OR Notification, Maintenance Plan OR Maintenance Item".
But i am able to create measurement document for equipment / FL having user status DCM with Transaction control Forbidden of Measurement document creation. No error message displayed by the system.
Can anybody tell me why its happening? Why system is giving error during order & plan creation but not for Creation of measurement document ?
If this is not posible in standard SAP, does any body knows about any OSS note so that we can implement the same to get an error message.
Thanks in advance
Arun

Please ensure whether both projects have the same budget profile. Other than that you need to carefully investigate how the cost was posted onto both projects in the first place. Please note in case of procurements, budget is only checked at the commitments level (search the forum as this has been discussed before).
In case this does not resolve your issue, revert back with the budget profile settings.
Regards,
Ammar

Use of business transaction variant in QM notification

Dears
I have a issue with notification.
I have defined action box as below
SPRO>Quality Management>Quality Notifications>Notification Processing>Additional Notification Functions>Define Action Box>Define Functions for the Action Box
For a notification type, I have defined 3 actions
Yes, NO, TBD
I am usiong std function module - QM06_FM_TASK_SEND_PAPER in function and QM06_SEND_PAPER_STEP2 FM when saving field.
The difference is Code and code group + business transaction attached to above 3 action
for Yes - code gropup/code is ACTION/YES, business transaction - QN74
for N0   - code gropup/code is ACTION/NO - business transaction - QN75
for TBD - code gropup/code is ACTION/TBD - business transaction - QN71
I have created user status with status as Yes/No/TBD
I have attached thebusiness transaction(QN74, QN75, QN7 created aboveto user status status, Yes/No/TBD respectvely. "allowed and set" in OIBS-user status maintenance.
Hence while on clicking on action in QM notificatioon systems does 2 things
Task creation with code and code group mention above
User status mention above.
Till here it is fine, by mistake user clicked on No and he wants to change it to Yes...system is not allowing him to change it gives popup error that " The function you selected cannot be carried out: - Follow-up function: Variant 5", when I click on detailed info, no status is shown as preventing this action.
Did any one faced this type of problem? Is it a bug? Please help me.

hi
can you post the status profile you have created with the status number and the lowest and highest number,if for example you have status number as 10,20,30 for each status you can maintain the low and highest number
10        10   20
20        20   30
30        30   30
hence if the status number 20 is activated either you can assign the status with status no 30 and reassign with the same status number 20 you cannot able to reassign to 10 since lowest number is not between the limits
regards
thyagarajan

Business Transactions and Document Types

Hi eXperts !
Can anyone please explain these business transactions like when they are created, what is the document type related to these.
KOAE     Actual Settlement CO External
RFBU     FI Postings
COIN     CO Interface
RKU1     CO Act. Primary Cost Transfer
KOAR
Actually I need to extract a report in Project systems with actual amount paid to the vendor + all the actual cost but it shows only down payment (doc. type KA if i am not wrong) not the final payment.
Also please explain these document types because i can see them in my report but I dont really know what does it mean.
AA     Asset posting
AB     Accounting document
KA     Vendor document - This type of doc. is created when we do Down-payment to vendor (correct me if m wrong)
TZ     Vendor Document
KZ     Vendor payment - Doc. created when we do Actual Payment to vendor (correct me if m wrong)
SA     G/L account document
KG     Vendor credit memo
Rabiee

Any thoughts ?

Business Transactions and Document type

Hi eXperts !
Can anyone please explain these business transactions like when they are created, what is the document type related to these and which one should I use to see the Amount paid to the Vendor (Actual Payment)
KOAE     Actual Settlement CO External
RFBU     FI Postings
COIN     CO Interface
RKU1     CO Act. Primary Cost Transfer
KOAR
Actually I need to extract a report in Project systems with actual amount paid to the vendor + all the actual cost but it shows only down payment (doc. type KA if i am not wrong) not the final payment.
Also please explain these document types because i can see them in my report but I dont really know what does it mean.
AA     Asset posting
AB     Accounting document
KA     Vendor document
TZ     Vendor Document
KZ     Vendor payment
SA     G/L account document
KG     Vendor credit memo
As these things can be better explained by FICO guys so I decided to put the question here, Thanks alot !
Rabiee

Thanks for the reply AP
I'll check KZ doc. type
what about other document types and business trans. ?

Document Splitting issue - Business Transaction

Hi SDN,
I would just like to seek advise on our issue for Document Splitting, specifically on the business transaction.
We understand that you assign this business transaction to document types.
For our case however, we do have intercompany transactions, wherein we post to an Intercompany AP and Intercompany AR.
That means we both have AR and AP items in one document.
My question now is which business transaction should we assign to this Intercompany Document Type?
I've checked the selections and these are the only business transactions that we can use.
0000     Unspecified posting
0100     Transfer posting from P&L to B/S account
0200     Customer invoice
0300     Vendor invoice
0400     Bank account statement
0500     Advance tax return (regular tax burden)
0600     Goods Receipt for Purchase Order
1000     Payments
1010     Clearing transactions (account maint.)
1020     Resetting cleared items
I would like to seek advise from those who has implemented Document Splitting before.
Thanks!

Dear,
I have never tried to consolidate both IC AR and IC AP document type.
Ideal it should be bifurcated as AP and AR because for One company it will be Sale and other will be Purchase.
Please bifurcate the same and then do the configuration related to Document Splitting.
Hope this helps!!
Br Vivek
Pls assign points for appropriately.

G/L account cannot record in the business transaction.

Dear Experts,
When i am using cash journal (FBCJ), some G/L account cannot record in the business transaction. (error msg: you cannot enter tax code in business transaction).
I want to know how to edit the business transaction to disable the tax code requirement for those G/L account
Regards,
Wilson

Hi
If you want to disable the tax code requirement for that particular GL a/c XXXXX.
1) In FS00 Please chck if there is any tax category specified(under control data tab), please ensure that no tax code is specified.(this particular chk mark will make the gl account as tax relevant)
2) if no tax code specified in fs00, you need not specify anything in the transaction code FBCJC2 (For that business transaction) in the field tax code.
3) So at the time of posting transaction in FBCJ it will not give any error.

Cash Journal - Business transaction (Expense) - Tax information

Dear all,
When I post a business transaction (type E - Expense) via Cash Journal FBCJ, by example: Payment for flowers, I want to add Tax information into this document (i.e: VAT number) for reporting later. But I don't know where to input this information. Could you please help me ?
Thank you very much for your help,
Best regards,
Sylvecat

hi,
there will be one tax column in that u can give the tax code, if u want to give vat number like that means u can give it in the vendor master record.

Subledger posting in Derived Business Transactions

Similar Messages

Maybe you are looking for