Posting key in FB70 t-code

Dear all,
FB70 tcode will ,by default, takes posting key 01, if you select credit memo it will take 11. is there any way to change the posting key 12 in FB70 for my testing scenarios.
How can i change the posting key in FB70 t-code.
Regards,
Suresh Patipati.

Advice not to change standard settings. For information purpose you could visit OBXW transaction, for transactin AGD, you could see where the posting keys are set to default.

Similar Messages

Please help with Posting Keys For Fast Entry (t.code OBXJ)

Dear experts,
Please help me to be more familiar with configurtation of Enjoy Transactions (t.code OBXJ). I want to configure fast entry transaction and change standard assignement of posting key. But there are no editing options in this transaction, just three transaction keys are predefined and posting keys are assigned to them (those are changable). But where to see what those transaction keys mean? And what could be your proposals, how to configure this IMG step?
Thanks!

Hi,
t.code OBXJ is for automatccly postings, normal you never change the standard posting keys.
In the block line items you can select colums you need and place the one's you need to the begin of the screen and in the right top corner of posting line items you can click an save this as (default) variant.
When you want to use an other posting keys you use the option complex posting (F6)
Paul

How posting key is taken up when we generate accounting document

hi ,
i am trying to bill a customer using billing type RE which is credit for returns. but when i generate posting document instead of crediting the customer account its getting debited ie) it is taking up the posting key 01 instead of 11 .
how this posting key is determined when we generate accounting documnet .
if u have any questiin or clarification kindly ask me.
thanks

hi,
start with checking OBXW, here you check the customer item outgoing invoice, where you will find posting keys assigned for debit and credit. Might be its configured wrongly here.
Second, Check T.code OB40 this is where we tell what type of accounts are affected with this posing key and is the effect a debit or credit. You have radio buttons for it.
But remember these are all standard SAP config settings and i guess there would really be a need to change them here if not while practising.... Make the settings as required and do consult an FI guy on this.
regards
sadhu kishore

Maintain acct determination (table T030B) for posting key IRX / IGX (M8395)

Dear Guru,
I am testing IS-Oil & Gas (Downstream) - Exchanges.
Created Exchange Agreement and Purchase Contract and Sales Contract, Purchase Contract and Sales Contract are assigned to the Exchange Contract.
A PO is created with reference to the Purchase Contract.
Upon post goods receipt in MIGO, encountered error message "Maintain account determination (table T030B) for posting key IRX (Message no. M8395)" that does not allow PGR to get through.
A call-off is created with reference to the Sales Contract.
Similarly, when PGI is performed in VL01N, encountered error message "Maintain account determination (table T030B) for posting key IGX (Message no. M8395)" that does not allow PGI to get through.
Checked in OBYC, there is no transaction key for IRX and IGX.
Please advise. Thank you.
Regards,
WL

Hi WL,
Please use transaction code O54E to maintain the required configuration.
I hope this helps you.
Thanks & Regards
Kalpesh Chavda

FB60 - Two line items for tax amount (Posting Key - 50)

Hi,
I am facing some issue in FB60 invoice posting. For the same vendor(say V1) I am posting 2 different invoices for 100 USD - the company code, G/L, CostCenter & Tax Jursdiction code are different in both the cases. Once I do FB60 and got to document overview screen this is what I see...
Case1 - in the document overview screen I see a Posting key(PK) 31(invoice amount), PK50(tax amount) & PK40(total amount)...which is fine.
Case2 - in second case the document overview shows two line items for PK50(credit - tax amount) and tax amount is different.
Two questions...
1) Why there are two tax items (PK50 items) - is that dependent on tax rule or vendor or company code?
2)My client says the tax amount should be same in both cases - but I am wondering how can it be, when tax codes are different in both the cases? Where can I check how these tax values are getting calculated.
Any adivse/hints will be greatly appreciated/rewarded.
Thanks
Kiran

AKu
I got the same scenario also
this second document display because of material price change u can double click that document

Post with clearing through transaction code f-04

Hi
While clearing the Gl account Manually with transaction code F-04 we
are getting the Error Consolidated companies SASA and ' ' are different
Diagnosis
The number of the affiliated company must be clear for the selected
document type for all line items. In this case at least two different
companies or a company in connection with a business partner who does
not belong to a company are stated.
Procedure
If you selected the correct accounts, you must enter the document with
a document type that allows cross-company posting. Otherwise, please
correct the entered account.
Please help in this matter. This is bit urgent
Regards
Vinay Bhaskar

Hi Manasi,
As the name suggest, F-04 allows you to POST to one account by CLEARING another account.
For example you have a provision account which needs to be adjusted when the actual expense is paid - this how it will be done -
Give the document header details, select "Transfer posting with clearing", enter the posting key (40), give the GL account (expense account as per the example) and go to the next screen.
Give the amount and other details for the line items and then select "choose open item" from the menu. The new screen will ask you to give an account where you will give the provision account (the account from which the open item needs to be cleared).
Press enter and you will get the list of open items for the GL account from where you can proceed like any other clearing.
Hope this clarifies. Do revert in case of any further queries.
Thanks and Regards,
anit

How to find out the table for Posting Key and A/R & A/P Document types

hi folks,
can you let me know which TABLE is used to Posting key and also which TABLE is used for Account Receivables and Account Payables.
Thank you in advance.

To find the table of posting key, select any posting key at OB41, then press F1, then click on hammer icon the table used will be displayed. For Posting Key TBSL is the table used.
Posting Key TBSL
Customer Master (General) KNA1
Customer Master (Company Code) KNB1
Vendor Master (General) LFA1
Vendor Master (Company Code) LFB1
Satish
(please close the thred if u satisfiy with the answer)

BAPI FUNCTION MODULE BAPI_ACC_DOCUMENT_POST : How to give posting keys?

Hi ,
i am using BAPI_ACC_DOCUMENT_POST to post accounting document. This accounting document is used to post amount from reconcilation account to bank GL account.the table parameter am using is ACCOUNTGL (in the function module)Now i want to give posting keys to the function module parameter. can anyone please guide me how to give posting keys?
Edited by: Santhosh Kumar Cheekoti on Dec 18, 2008 7:48 AM

Hi,
As pointed out in one of the previous post, posting key will be decided by the BAPI depending on the sign of the amount. Have a look at bthe following code:-
DATA: doc_header LIKE BAPIACHE09,
      criteria   LIKE BAPIACKEC9 OCCURS 0 WITH HEADER LINE,
      doc_item   LIKE BAPIACGL09 OCCURS 0 WITH HEADER LINE,
      doc_ar     LIKE BAPIACGL09 OCCURS 0 WITH HEADER LINE,
      doc_values LIKE BAPIACCR09 OCCURS 0 WITH HEADER LINE,
      return     LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
      extension1 like BAPIACEXTC occurs 0 with header line,
      obj_type   LIKE bapiache08-obj_type,
      obj_key    LIKE bapiache02-obj_key,
      obj_sys    LIKE bapiache02-obj_sys,
      docnum     LIKE bkpf-belnr.
*DATA:
*       ITEMNO_ACC     POSNR_ACC
*       FIELDNAME     FIELDNAME
*       CHARACTER     ACPI_RKE_CRIGEN
* Fill Document Header
doc_header-bus_act = 'RFBU'.
doc_header-bus_act = 'RMRP'.
*doc_header-bus_act = 'SD00'.
doc_header-username = sy-uname.
doc_header-header_txt = 'TEST BOC BAPI POSTING'.
doc_header-comp_code = 'IN10'.
doc_header-compo_acc = 'FICA'.
doc_header-doc_date = '20060127'.
doc_header-pstng_date = sy-datlo.
doc_header-doc_type = 'SA'.
** Fill Line 1 of Document Item
*doc_item-itemno_acc = '1'.
*doc_item-gl_account = '0000500001'.
*doc_item-pstng_date = sy-datum.
*doc_item-item_text = 'TEST POSTING DEBIT ITEM'.
*doc_item-costcenter = ''.
*doc_item-quantity = '1'.
*doc_item-base_uom = 'ST'.
*APPEND doc_item.
*CLEAR doc_item.
** Fill Line 2 of Document Item
*doc_item-itemno_acc = '2'.
*doc_item-customer = '0000000016'.
*doc_item-gl_account = '0000000016'.
*doc_item-pstng_date = sy-datlo.
*doc_item-item_text = 'TEST POSTING CREDIT ITEM'.
*APPEND doc_item.
*CLEAR doc_item.
doc_ar-itemno_acc = '1'.
doc_ar-gl_account = '0000500001'.
doc_ar-pstng_date = sy-datum.
doc_ar-item_text = 'TEST POSTING DEBIT ITEM'.
doc_ar-costcenter = ''.
doc_ar-quantity = '1'.
doc_ar-base_uom = 'ST'.
APPEND doc_ar.
CLEAR doc_ar.
* Fill Line 2 of Document Item
doc_ar-itemno_acc = '2'.
doc_ar-customer = '0000000016'.
doc_ar-gl_account = '0000000016'.
doc_ar-pstng_date = sy-datlo.
doc_ar-item_text = 'TEST POSTING CREDIT ITEM'.
doc_ar-stat_con = ' '.
doc_ar-costcenter = '0000201681'.
APPEND doc_ar.
CLEAR doc_ar.
* Fill Line 1 of Document Value.
doc_values-itemno_acc = '1'.
doc_values-currency_iso = 'INR'.
doc_values-amt_doccur = '200.00'.
doc_values-currency = 'INR'.
doc_values-CURR_TYPE = '00'. "Doc currency
APPEND doc_values.
CLEAR doc_values.
* Fill Line 2 of Document Value
doc_values-itemno_acc = '2'.
doc_values-currency_iso = 'INR'.
doc_values-amt_doccur = '200.00-'.
doc_values-currency = 'INR'.
doc_values-curr_type = '00'. "Doc currency
APPEND doc_values.
CLEAR doc_values.
* Add tax code in extension1 table.
extension1-field1 = 'BAPI CALL'.
APPEND EXTENSION1.
* Fill CRITERIA for CO-PA
*refresh criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'ARTNR'.
*criteria-CHARACTER     = '000000000001312251'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'WERKS'.
*criteria-CHARACTER     = 'IN91'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'KNDNR'.
*criteria-CHARACTER     = '0000000016'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'FKART'.
*criteria-CHARACTER     = 'ZIN2'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'KAUFN'.
*criteria-CHARACTER     = '0000000633'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'KDPOS'.
*criteria-CHARACTER     = '000010'.
*Append criteria.
*criteria-ITEMNO_ACC = '1'.
*criteria-FIELDNAME     = 'VKGRP'.
*criteria-CHARACTER     = '009'.
**Append criteria.
* All tables filled - now call BAPI.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
EXPORTING
    documentheader       = doc_header
IMPORTING
    OBJ_TYPE             = doc_header-obj_type
    OBJ_KEY              = doc_header-obj_key
    OBJ_SYS              = doc_header-obj_sys
TABLES
*    criteria             = criteria
    accountgl            = doc_item
    ACCOUNTRECEIVABLE    = doc_ar
    currencyamount       = doc_values
    return               = return
    EXTENSION1           = EXTENSION1.
LOOP AT return WHERE type = 'E'.
EXIT.
ENDLOOP.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
EXPORTING
    documentheader       = doc_header
IMPORTING
    OBJ_TYPE             = doc_header-obj_type
    OBJ_KEY              = doc_header-obj_key
    OBJ_SYS              = doc_header-obj_sys
TABLES
*    criteria             = criteria
    accountgl            = doc_item
    currencyamount       = doc_values
    return               = return
    EXTENSION1           = EXTENSION1.
LOOP AT return WHERE type = 'E'.
EXIT.
ENDLOOP.
IF sy-subrc EQ 0.
WRITE: / 'BAPI call failed - debug and fix!'.
ELSE.
CLEAR return.
REFRESH return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
* EXPORTING
*   WAIT          =
   IMPORTING
     return        = return.
WRITE: / 'BAPI call worked!!'.
WRITE: / doc_header-obj_key, ' posted'.
ENDIF.
Regards
Raju Chitale
Edited by: Raju Chitale on Dec 18, 2008 8:31 AM

Very high LC amounts in GL view and missing posting keys inGL view

Hi Experts,
Doc.type : KR
Transaction: FB60
Document currency PLN = Local currency PLN
in general ledger view of a document the items of vendor reconciliation account and of a balance sheet account with currency PLN in master data , have huge amounts which are much more higher than entered amounts in entry view.
For some items Posting key is missing and the total of items does not balance to zero.
The expense account items of the document have same amount as entere in the entry view.
Company code currency is PLN, Document currency and local currency both are PLN.
Furthermore 2 items of reconciliation account does not have in general ledger view any posting key and the total balance of the items are not balanced to zero in GL view.
The company have ECC6.0 and document splitting is active and was working fine.
The company has EUR as hard currency and USD as group currency.
I look forward to your feedbacks.
Thanks and Kind Regards

Hi ,
Can you Please look at OSS note
1655571 - Multiple values and multiple/additional line items appearing in the NewGL View when compared to Entry View
Many Thanks

Generate 2 line items with posting keys in same table while using FM .

Dear Expert ,
For T-code f-65 ,I have to park a FI Document .i tried with PRELIMINARY_POSTING_FB01 for parked Document . But i am not successfully park the document .
with the help of F-65 the data Segregate between Tables VBSEGS and VBSEGD with respecting Posting key . but with this Fm entire entry is displaying in table VBSEGS .For example it generated two line items with posting keys '15' and '40' and these both are displayed in VBSEGS whereas posting key '15' has to be displayed in VBSEGD.
when i check this Document in FBV0 Error reflect " G/L Account 0012000 1001 Does not Exist ".
Here my code -
DATA:   XT_BKPF LIKE BKPF OCCURS 0 WITH HEADER LINE ,
        XT_BSEG LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEG1 LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEC LIKE BSEC OCCURS 0 WITH HEADER LINE ,
        XT_BSET LIKE BSET OCCURS 0 WITH HEADER LINE ,
        XT_BSEZ LIKE BSEZ OCCURS 0 WITH HEADER LINE ,
        XT_BKORM LIKE BKORM OCCURS 0 WITH HEADER LINE ,
        XT_THEAD LIKE THEAD OCCURS 0 WITH HEADER LINE ,
        XT_SPLTTAB LIKE ACSPLT OCCURS 0 WITH HEADER LINE ,
        XT_SPLTWT LIKE WITH_ITEMX OCCURS 0 WITH HEADER LINE .
DATA :    XTEXT_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XTEXT_ITEM_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XI_UF05A LIKE UF05A,
          XI_XCMPL TYPE XFELD VALUE 'X',
          XFS006_FB01 LIKE FS006 ,
          XI_TCODE LIKE T020-TCODE VALUE 'F-65',
          XI_PARGB LIKE RF05A-PARGB        ,
          XI_TCODE_INT TYPE TCODE           .
DATA P_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
XT_BKPF-BUKRS     =     'CP01'.
XT_BKPF-GJAHR     =     2011.
XT_BKPF-BLART     =     'DZ'.
XT_BKPF-BLDAT     =     SY-DATUM.
XT_BKPF-BUDAT     =     SY-DATUM.
XT_BKPF-MONAT     =     '06'.
XT_BKPF-CPUDT     =     SY-DATUM.
XT_BKPF-WWERT     = SY-DATUM.
XT_BKPF-USNAM     =     'ABAPER'.
XT_BKPF-TCODE     =     'F-65'.
APPEND XT_BKPF.
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '001'.
XT_BSEG-BSCHL = '40'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'S' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = '241000'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
Vendor line item - required even for header only - BSEG table
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '002'.
XT_BSEG-BSCHL = '15'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'H' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = 'PC04000001'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
CALL FUNCTION 'PRELIMINARY_POSTING_FB01'
   EXPORTING
     TEXT_UPDATE            = XTEXT_UPDATE
     TEXT_ITEM_UPDATE       = XTEXT_ITEM_UPDATE
I_UF05A                =
     I_XCMPL                = XI_XCMPL
FS006_FB01             =
      I_TCODE                = XI_TCODE
I_PARGB                =
I_TCODE_INT            =
IMPORTING
    XEPBBP                 = CHECK_A
    TABLES
      T_BKPF                 = XT_BKPF
      T_BSEG                 = XT_BSEG
      T_BSEC                 = XT_BSEC
      T_BSET                 = XT_BSET
      T_BSEZ                 = XT_BSEZ
T_BKORM                =
T_THEAD                =
T_SPLTTAB              =
T_SPLTWT               =
          EXCEPTIONS
            ERROR_MESSAGE = 1.
P_RETURN-ID         = SY-MSGID.
P_RETURN-TYPE       = SY-MSGTY.
P_RETURN-NUMBER     = SY-MSGNO.
APPEND P_RETURN.
     p_return-MESSAGE_V1 = XSYMSGV.
IF SY-SUBRC = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
ENDIF.
WRITE :/ sy-subrc , sy-MSGV1 .
Thanks ,
Ashish Gupta

Hi Raghuram,
I found a very important SAP Note 103051, details are below.
An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
Other terms
INVOIC, SAPLIEDI, M8047, M8, 321
Reason and Prerequisites
This is because of the program design.
Solution
There is no solution for IDOC_INPUT_INVOIC_MM.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
Hope this helps.
Reward if helpful.
Thanks

Posting Key in BAPI_ACC_DOCUMENT_POST

Hi,
I am using bapi 'BAPI_ACC_DOCUMENT_POST' to post 'Customer Document' in FB01. I was able to post the document but Posting Key in the document is not as desired. When I try to Post the document with out any Posting Key by default I am having Posting Key as '01'(Customer document) and '50'(GL account).
But I want bapi 'BAPI_ACC_DOCUMENT_POST' to post a document with Posting key '15'(Customer Document) and '40'(GL account).
In bapi I am using these tables along with header.
ACCOUNTGL- GL Account
ACCOUNTRECEIVABLE- Customer Document
I tried passing the posting key in ACCT_TYPE in table ACCOUNTGL and passing the the posting key using EXTENSION2 table but was not successful .
Can anyone let me know
How can I pass the Posting Key to the bapi 'BAPI_ACC_DOCUMENT_POST' for Customer Document and GL account?
OR
How can I use EXTENSION2 table to create an appropriate posting key?
please let me know.
Vikki,
In one of your thread you came across the same issue and you solved it. Can you please guide me how to achive appropriate posting key using EXTENSION2 table?
Thanks,
Vijay.

Hi,
Just follow these steps:
1. Fill in your EXTENSION table like this
first 3 character represent item number
next 2 character represent posting key
CLEAR: gt_extension.
gt_extension(3) = sy-index(3).
gt_extension+3(2) = 'New Posting Key'.
APPEND gt_extension.
2. Create an FM similar to SAMPLE_INTERFACE_RWBAPI01 and put the following codes:
IF NOT extension IS INITIAL.
LOOP AT extension.
 READ TABLE it_accit WITH KEY posnr = extension(3).
 IF sy-subrc IS INITIAL.
 it_accit-bschl = extension+3(2).
 MODIFY it_accit INDEX sy-tabix.
 ENDIF.
ENDLOOP.
ENDIF.
3.
- Go to TCode "FIBF".
- Go to Settings -> Products -> ... of a customer
- Create a new entry and check the box to activate the product
Product = <any name>
Text = <description>
RFC = blank
Check the activation box
- Go to Settings -> Process Modules -> ... of a customer
- Create a new entry by specifying the name of the function module name and product name created earlier.
Process = RWBAPI01
Ctr = blank
Appl = blank
FM = <FM created>
Product = <name of product created earlier>
Hope this helps,
Leonard Chomi.

How to mention posting keys for line items in IDOCS for fb01 posting

Hi all ,
I am using IDOCS for fb01 posting with posting keys 15 and posting keys 40 for line items .The data is in legacy file . I am using IDOC ACC_GL_POSTING_01 for posting . Is there any way that I can mention the posting keys in the segment parameters of the IDOC.If there is anyone who have done fb01 posting with IDOCS,please help me with the code .Please treat the question as urgent .
Thanks in advance

Hi Arshad,
There is no fecility to enter Posting keys explicitly.. It is determined automaticall by the Credit/Debit amounts u enter in GL data in the segments E1BPACGL08 and E1BPACCR08 and also it depends on the Customer and Vendor no.
Sreedhar

GL account and posting keys

Hi All,
Can someone guide me how the Debit and the creift indicator is determined for the system to post the accouting entry for a sales transaction.
Through account determination the GL account is determined for an account key.
For example if GL account for sales determined is 1234 through account key. How does the system determines whether a credit value appears against the GL account 1234 (through posting key 50) and how the system determines the corresponding debit entry (posting key 40) to the customer account.
Can some show the T codes or menu path to link the GL accounts to posting keys and how the system determines that for every credit to sale account , a corresponding debit needs to be done to customer account (what control this )
regds

Dear Friend,
As you already know the accounting Principles, that Debit & Credits & every postings should be equal.
Now as per GL account determination maintained system determines necessary GL Accounts.
Now, in GL Account Definition (T-Code FS00) you enter Account Group (e.g. Inventory account, Fixed Asset account, Account Receivable, etc)
This Account Group classifies the GL Account Master Data. The account group is a classifying feature within the G/L account master records. The account group is a required entry.
The account group determines the fields for the entry screens if you create or change a master record in the company code. The account group also determines in which number interval the account number must be.
Hope this helps...
Thanks,
Jignesh Mehta

Posting Keys for Account Determination do not exist

This doubt in STO scenario:
STO - between 2 plants - different company codes under same client
Created STO from Receiving Plant in ME21N with document type NB
Based on that STO, Created Delivery in VL10B from supplying Plant
Tried PGI in VL02N from supplying Plant.
Received the Error Message as below:
Posting keys for account determination for transaction BUV do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction BUV have not been set.
System Response
Because the posting key is missing, the system cannot generate any automatic postings.
Procedure
Maintain the posting keys necessary for transaction BUV.
kindly give the solution and advance thanks.
Vaidee

Hi Vadee,
Account Determination for BUV has not been setup for PGI.
So , go to transaction OBYC and assign the account by double clicking BUV and give u r chart of accounts and check whether the account has been maintained. If not maintain.
If account has been maintained , select your account/valuation class and select posting keys push button and maintain the posting keys.
Regards,
Nani

Relation Between Dummy Profit Center and Posting Keys.

Hello Gurus,
It will be a valuable feed back for below mentioned Scenario.
One of our client is on SAP Version 4.7 and New GL is not activated. In COCD one Customer Invoice entry is booked as below.
PK     Account           Amount      Profit Center
01     SURXXX1            100.00         ABCD
50     REVENUE A/c      50.00         ABCD
50     ENT TAX               20.00         ABCD
50     SERVICE TAX       30.00         ABCD
After running t codes 1KEK, F.5D, and KE5T for customer line item system picks same profit center as mentioned in other line items i.e ABCD.
But when we reverse the above document system picks DUMMY Profit center instead of ABCD.
PK     Account           Amount      Profit Center
12     SURXXX1            100.00         DUMMY
40     REVENUE A/c      50.00         ABCD
40     ENT TAX               20.00         ABCD
40     SERVICE TAX       30.00         ABCD
Basically we have checked field status variant for Posting Key 01 and 12 in which Profit Center field is Required and field status for profit center for reconciliation account is also required. This is unusual behavior which we are facing right now.
Regards,
Ajinkya Ahire

Profit Center :
A profit center is a management-oriented organizational unit used for internal controlling purposes. Dividing your company up into profit centers allows you to analyze areas of responsibility and to delegate responsibility to decentralized units, thus treating them as "companies within the company". EC-PCA lets you set up your profit centers according to product (product lines, divisions), geographical areas (regions, offices or production sites) or function (production, sales).
Profit Center Accounting (PCA) allows you to calculate internal measurements of profitability. This internal view of profitability, then, reflects the success of a given profit center at meeting the profitability goal for which it was given responsibility.
Cost Center :
The cost center is an organizational unit in a controlling area. Cost centers can be defined according to several different design approaches. A typical approach could be for an enterprise to define a cost center for each low-level organizational unit that has responsibility for managing costs. As costs are incurred, they are assigned or posted to the appropriate cost center. These costs could include payroll costs, rent and utility costs, or any other costs assignable to a given cost center.
Each cost center is assigned to a category, e.g. Administration cost center, production cost center, etc. Each cost center master record has a field for the name of the person responsible for the cost center.
For detailed information go thru the below article
https://wiki.sdn.sap.com/wiki/display/ERPFI/BasicConceptsof+Controlling
Hope this helps.
Cheers,
Srinath.

Posting key in FB70 t-code

Similar Messages

Maybe you are looking for