Acc Assignment Release

Hi,
We have release procedure setup for PO, but also need to have release procedure triggered for any changes in PO for G/L account. Should we maintain this a seperate characterisitic and assign to class.
Thanks....

Hi,
SAP Standard release procedure wont check GL account changes for release strategy determination. Hence you can use some BADI's/User exits through which you can check GL account changes to redetermine PO release.
Creating a class/characteristic wont work to meet your above requirement.
Thanks & Regards,

Similar Messages

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

Acc. assignment in PO

Hi all,
I have urgent problem.
I created PO with K (cost center) acc. assign., entered Cost center and automatically got expense account. Created GR and posted expense acc.&GRIR clearing account.
In Miro it should be vendor & GR/IR clearing and tax.
There comes problem, I get error message: "Account ### can not be posted to Cost Center".
It seems the problem is GR/IR clearing account.
It is not allowed to have assigned cost center? But actually cost center is assigned in PO with acc.assignemet?
Are there some settings that I am missing? Or wrong definition of account or something else?
Please, urgently advice.
Thanks

Hi,
Ofcourse I have a valuation class, that is not a problem, system see all accounts as it should. I think that the problem is with definition of account, does anybody knows which field in master data of account is controling this settings?
In any case, it is clearing account and it should not be in P&L accounts in controling?
It is not a automatic posting, nor supplement, can it be field status?
Thanks,
Anchi

BAPI_PO_CREATE1 - In case of account assignment, please enter acc. assignment data for item

Hi,
Currently I'm facing an error "In case of account assignment, please enter acc. assignment data for item" when create a Purchase Order using BAPI_PO_CREATE1. The condition of the data that need to pump into the system is that this PO is an open item PO where does not require a metarial code for input, but it will pump in Short Text and Material Group. Other than that, the account assignment category is "K" and the item category is "9".
Below is the coding that I have implemented.
IF wa_temp_upr1-waers IS NOT INITIAL.
       MOVE wa_temp_upr1-waers TO wa_header-currency.
       wa_headerx-currency = abap_true.
     ENDIF.
     MOVE: wa_temp_upr1-lifnr TO wa_header-vendor,
           wa_temp_upr1-unsez TO wa_header-collect_no,
           wa_temp_upr1-bukrs TO wa_header-comp_code,
           sy-datum      TO wa_header-doc_date,
           sy-langu      TO wa_header-langu,
           'KTN1'        TO wa_header-purch_org,
           wa_temp_upr1-bkgrp TO wa_header-pur_group,
           wa_temp_upr1-zterm TO wa_header-pmnttrms.
     wa_headerx-collect_no = abap_true.
     wa_headerx-po_number = abap_true.
     wa_headerx-comp_code = abap_true.
     wa_headerx-vendor = abap_true.
     wa_headerx-doc_date = abap_true.
     wa_headerx-langu = abap_true.
     wa_headerx-purch_org = abap_true.
     wa_headerx-pur_group = abap_true.
     wa_headerx-pmnttrms = abap_true.
     IF wa_temp_upr1-meins IS NOT INITIAL.
       MOVE wa_temp_upr1-meins TO zunit_e.
       CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'
         EXPORTING
           INPUT                = zunit_e
           LANGUAGE             = 'E'
         IMPORTING
           OUTPUT               = zunit_e.
       IF SY-SUBRC <> 0.
* Implement suitable error handling here
       ELSE.
         MOVE zunit_e TO wa_temp_upr1-meins.
       ENDIF.
       MODIFY it_upr1 FROM wa_temp_upr1.
     ENDIF.
     ADD 10 TO line_item.
     CALL FUNCTION 'NUMBER_GET_NEXT'
       EXPORTING
         NR_RANGE_NR = '01'
         OBJECT      = 'SERVICE'
       IMPORTING
         NUMBER      = pckg_no.
     IF SY-SUBRC <> 0.
* Implement suitable error handling here
     ENDIF.
     CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
       EXPORTING
         INPUT = wa_temp_upr1-matnr
       IMPORTING
         OUTPUT = wa_po_item-material.
     MOVE: line_item TO wa_po_item-po_item,
           wa_temp_upr1-ewerks TO wa_po_item-plant,
           wa_temp_upr1-lgort TO wa_po_item-stge_loc,
           wa_temp_upr1-matnr TO wa_po_item-material,
           wa_temp_upr1-menge TO wa_po_item-quantity,
           wa_temp_upr1-peinh TO wa_po_item-price_unit,
           wa_temp_upr1-netpr TO wa_po_item-net_price,
           wa_temp_upr1-meins TO wa_po_item-po_unit,
           wa_temp_upr1-afnam TO wa_po_item-preq_name,
           wa_temp_upr1-eeind TO wa_po_item-price_date,
           ' ' TO wa_po_item-gr_ind,
           'X' TO wa_po_item-ir_ind,
           'X' TO wa_po_item-prnt_price,
           ' ' TO wa_po_item-distrib.
     wa_po_item-acctasscat = 'K'.
     MOVE pckg_no TO wa_po_item-pckg_no.
     wa_po_itemx-pckg_no = abap_true.
     IF wa_temp_upr1-bismt IS INITIAL.
       MOVE: wa_temp_upr1-short_text TO wa_po_item-short_text,
             wa_temp_upr1-matl_group TO wa_po_item-matl_group,
            '9' TO wa_po_item-item_cat.
       wa_po_itemx-short_text = abap_true.
       wa_po_itemx-matl_group = abap_true.
       wa_po_itemx-item_cat = abap_true.
       wa_potext-po_item = wa_po_item-po_item.
       wa_potext-text_id = 'F01'.
       APPEND wa_potext TO it_potext.
     ENDIF.
     MOVE wa_po_item-po_item TO wa_po_itemx-po_item.
     wa_po_itemx-plant = abap_true.
     wa_po_itemx-po_itemx = abap_true.
     wa_po_itemx-stge_loc = abap_true.
     IF wa_po_item-material IS NOT INITIAL.
       wa_po_itemx-material = abap_true.
     ENDIF.
     wa_po_itemx-quantity = abap_true.
     wa_po_itemx-price_unit = abap_true.
     wa_po_itemx-net_price = abap_true.
     wa_po_itemx-po_unit = abap_true.
     wa_po_itemx-preq_name = abap_true.
     wa_po_itemx-price_date = abap_true.
     wa_po_itemx-acctasscat = abap_true.
     wa_po_itemx-gr_ind = abap_true.
     wa_po_itemx-distrib = abap_true.
     wa_po_itemx-part_inv = abap_true.
     APPEND wa_po_item TO it_item.
     APPEND wa_po_itemx TO it_itemx.
     CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
           INPUT = wa_temp_upr1-kostl
         IMPORTING
           OUTPUT = wa_temp_upr1-kostl.
       wa_account-costcenter = wa_temp_upr1-kostl.
       ADD 1 TO l_acc.
       ADD 10 TO v_po_item.
       MOVE v_po_item TO wa_account-po_item.
       MOVE '01' TO wa_account-serial_no.
       APPEND wa_account TO it_account.
       wa_accountx-costcenter = abap_true.
       MOVE v_po_item TO wa_accountx-po_item.
       MOVE '01' TO wa_accountx-serial_no.
       wa_accountx-SERIAL_NOX = abap_true.
       wa_accountx-po_itemx = abap_true.
       APPEND wa_accountx TO it_accountx.
*********** services
       wa_services-pckg_no = pckg_no.
       wa_services-line_no = '0000000001'.
       wa_services-outl_ind = 'X'.
       wa_services-subpckg_no = pckg_no + 1.
       wa_services-quantity = wa_temp_upr1-menge.
       wa_services-base_uom = wa_temp_upr1-meins.
       wa_services-price_unit = wa_temp_upr1-peinh.
       wa_services-gr_price = wa_temp_upr1-netpr.
       IF wa_temp_upr1-short_text IS NOT INITIAL.
         wa_services-short_text = wa_temp_upr1-short_text.
       ENDIF.
       APPEND wa_services TO it_services.
       CLEAR: wa_services,
               val_lin.
       wa_services-pckg_no = pckg_no + 1.
       wa_services-line_no = '0000000002'.
       wa_services-quantity = wa_temp_upr1-menge.
       wa_services-base_uom = wa_temp_upr1-meins.
       wa_services-price_unit = wa_temp_upr1-peinh.
       wa_services-gr_price = wa_temp_upr1-netpr.
       IF wa_temp_upr1-short_text IS NOT INITIAL.
         wa_services-short_text = 'SERVICE 1'.
       ENDIF.
       IF NOT wa_temp_upr1-matl_group IS INITIAL.
         wa_services-matl_group = wa_temp_upr1-matl_group.
       ENDIF.
       APPEND wa_services TO it_services.
************* service account assignment
       wa_services_acc-pckg_no = pckg_no + 1.
       wa_services_acc-line_no = '0000000002'.
       wa_services_acc-serno_line = '01'.
       wa_services_acc-quantity = wa_temp_upr1-menge.
       wa_services_acc-serial_no = '01'.
       wa_services_acc-net_value = wa_temp_upr1-netpr.
       APPEND wa_services_acc TO it_services_acc.
       CALL FUNCTION 'BAPI_PO_CREATE1'
         EXPORTING
           POHEADER          = wa_header
           POHEADERX         = wa_headerx
           TESTRUN           = pa_test
           NO_PRICE_FROM_PO = 'X'
         IMPORTING
           EXPPURCHASEORDER = va_ebeln
           EXPHEADER         = wa_expheader
         TABLES
           RETURN            = it_return
           POITEM            = it_item
           POITEMX           = it_itemx
           POACCOUNT         = it_account
           POACCOUNTX        = it_accountx
           POSERVICES        = it_services
           POSRVACCESSVALUES = it_services_acc
           POTEXTITEM        = it_potext.
I have done some search regarding this error and try to implemented it, but still does not working.
example website that i found for this error is:
David Klein's Corner: SAP Purchase Order Creation Error via BAPI - "In case of account assignment, please enter acc…
PO Upload through BAPI_PO_CREATE1 - Problem in Service Item
Currently my system is using: SAP_APPL SAPKH60604
I am really stuck on this error. Hope you all can help me on this matter.
Thanks.

Hi,
Filling the service line have the problem,
while filling the services we must follow correct order,
Here You entering the new services, first manually create purchase order after that observe the table
'ESLL' and use the FM;-' MS_FETCH_SPEC_FOR_LIST' how the services are inserting after that you also follow the same order.
if service entries are created before the creation of the PO.
then follow as bellow....
SELECT * FROM esll INTO TABLE lt_esll WHERE packno = wa_tmp_spec-packno.
   IF sy-subrc = '0'.
     LOOP AT lt_esll.
       CLEAR : lt_poservices.
       lt_poservices-pckg_no    = lt_esll-packno .
       lt_poservices-line_no    = lt_esll-introw .
       lt_poservices-ext_line   = lt_esll-extrow .
       lt_poservices-outl_level = lt_esll-rang .
       lt_poservices-outl_no    = lt_esll-extgroup .
       lt_poservices-outl_ind   = lt_esll-del .
       lt_poservices-subpckg_no = lt_esll-sub_packno .
       lt_poservices-service    = lt_esll-srvpos .
       lt_poservices-edition    = lt_esll-ausgb .
       lt_poservices-ssc_item   = lt_esll-stlvpos .
       lt_poservices-ext_serv   = lt_esll-extsrvno.
       lt_poservices-quantity   = lt_esll-menge .
       lt_poservices-base_uom   = lt_esll-meins .
       lt_poservices-ovf_tol    = lt_esll-uebto .
       lt_poservices-ovf_unlim = lt_esll-uebtk .
       lt_poservices-gr_price   = lt_esll-tbtwr .
       lt_poservices-from_line = lt_esll-frompos .
       lt_poservices-to_line    = lt_esll-knt_introw.
       lt_poservices-short_text = lt_esll-ktext1 .
       lt_poservices-distrib    = lt_esll-vrtkz .
       lt_poservices-pers_no    = lt_esll-pernr .
       lt_poservices-wagetype   = lt_esll-lgart .
       lt_poservices-con_pckg   = lt_esll-knt_packno.
       lt_poservices-con_line   = lt_esll-knt_introw .
       lt_poservices-matl_group = lt_esll-matkl .
       lt_poservices-taxjurcode = lt_esll-txjcd.
       lt_poservices-tax_code   = lt_esll-mwskz .
       lt_poservices-date       = lt_esll-sdate .
       APPEND lt_poservices TO lt_poservices[].
       CLEAR lt_esll.
     ENDLOOP.
   ENDIF.
   CALL FUNCTION 'MS_FETCH_SPEC_FOR_LIST'
     EXPORTING
       spec_packno            = wa_tmp_spec-packno
*     ONLINE_DATA            = ' '
* IMPORTING
*     LIMIT                  =
     TABLES
       servicetab             = lt_ml_esll1
*     LIMITTAB               =
     EXCEPTIONS
       no_specification_exist = 1
       OTHERS                 = 2.
   IF sy-subrc <> 0.
* Implement suitable error handling here
   ENDIF.
   LOOP AT lt_ml_esll1 INTO DATA(ls_ml_esll1).
     CLEAR : lt_poservices.
     lt_poservices-pckg_no    = ls_ml_esll1-packno .
     lt_poservices-line_no    = ls_ml_esll1-introw .
     lt_poservices-ext_line   = ls_ml_esll1-extrow .
     lt_poservices-outl_level = ls_ml_esll1-rang .
     lt_poservices-outl_no    = ls_ml_esll1-extgroup .
     lt_poservices-outl_ind   = ls_ml_esll1-del .
     lt_poservices-subpckg_no = ls_ml_esll1-sub_packno .
     lt_poservices-service    = ls_ml_esll1-srvpos .
     lt_poservices-edition    = ls_ml_esll1-ausgb .
     lt_poservices-ssc_item   = ls_ml_esll1-stlvpos .
     lt_poservices-ext_serv   = ls_ml_esll1-extsrvno.
     lt_poservices-quantity   = ls_ml_esll1-menge .
     lt_poservices-base_uom   = ls_ml_esll1-meins .
     lt_poservices-ovf_tol    = ls_ml_esll1-uebto .
     lt_poservices-ovf_unlim = ls_ml_esll1-uebtk .
     lt_poservices-gr_price   = ls_ml_esll1-tbtwr .
     lt_poservices-from_line = ls_ml_esll1-frompos .
     lt_poservices-to_line    = ls_ml_esll1-knt_introw.
     lt_poservices-short_text = ls_ml_esll1-ktext1 .
     lt_poservices-distrib    = ls_ml_esll1-vrtkz .
     lt_poservices-pers_no    = ls_ml_esll1-pernr .
     lt_poservices-wagetype   = ls_ml_esll1-lgart .
     lt_poservices-con_pckg   = ls_ml_esll1-knt_packno.
     lt_poservices-con_line   = ls_ml_esll1-knt_introw .
     lt_poservices-matl_group = ls_ml_esll1-matkl .
     lt_poservices-taxjurcode = ls_ml_esll1-txjcd.
     lt_poservices-tax_code   = ls_ml_esll1-mwskz .
     lt_poservices-date       = ls_ml_esll1-sdate .
     APPEND lt_poservices TO lt_poservices[].
     CLEAR ls_ml_esll1.
   ENDLOOP.
   CLEAR : lt_poservices.
*& Filling the po service values internal table from service internal table
   LOOP AT lt_poservices[] INTO lt_poservices WHERE gr_price GT 0.
READ TABLE lt_ml_esll1 INTO wa_msll WITH KEY packno = lt_poservices-pckg_no
                                           introw = lt_poservices-line_no
                                        extrow = lt_poservices-ext_line..
     IF sy-subrc EQ 0.
       CLEAR lt_posvalues.
       lt_posvalues-pckg_no    = wa_msll-packno.
       lt_posvalues-line_no    = wa_msll-introw.
       lt_posvalues-quantity   = wa_msll-menge.
*      lt_posvalues-net_value = wa_msll-netwr.
       lt_posvalues-serno_line = '01'.
       lt_posvalues-serial_no = '01'.
*      lt_posvalues-percentage = '100'.
       APPEND lt_posvalues TO lt_posvalues[].
       CLEAR : wa_msll.
     ENDIF.
   ENDLOOP.
note:- if it is correct give points

RE: In case of account assignment, please enter acc. assignment data for it

Dear All,
I am getting the Error : 'In case of account assignment, please enter acc. assignment data for item'. when I try to create a service PO(I mean when the 'Item Cat' = 9 (D) and Account assignment category as K) .
I am populating POACCOUNT and POACCOUNTX structures of BAPI Correctly even the POSERVICES structure.
I tried even by creating through me21n, there it is getting created correctly. The order in which I am trying to enter in ME21N is First I am providing Org Data,
Next Item data with Acct assn cat as 'K' Item Category as 'D' short text, PO quantity, Order Unit, Net price, Material group, Plant,
Requisitioner.
Next it is prompting for Services data : short text, quantity, Unit, Gross price.
Then it is prompting for Account assignment of service in line 10, there I am giving GL account, Cost center.
It is creating the PO successfully.
But when I try using BAPI (BAPI_PO_CREARE1) it is giving the error 'In case of account assignment, please enter acc. assignment data for item'.
Please do the needful.
Thanks & Warm Regards,
Jayarama Krishna.

Dear All,
Who ever facing the above problem can use the below code, problem is solved.
When we create Purchase Order using "BAPI_PO_CREATE1", it works for all cases but we can have problems when we create Service Items in PO. Either we get an error u201CPlease maintain services or limitsu201D or u201CIn case of Account assignment, please enter acc. assignment data for itemu201D.
Service PO occurs when we enter item category u2018Du2019 (Service) and Account category u2018Ku2019 (Cost Center).
When we use BAPI_PO_CREATE1 to create service PO, following tables are populated at item level:
a) POITEM
b) POITEMX
c) POACCOUNT
d) POACCOUNTX
e) POSERVICES
f) POSRVACCESSVALUES
For service items: POITEM-PCKG_NO = u20180000000001u2019. (assign package no as a dummy number)
Set PCKG_NO flag in POITEMX table as u2018Xu2019.
Package No is the link that connect POITEM table to POACCOUNT table through tables POSERVICES and POSRVACCESSVALUES.
Set POACCOUNT-SERIAL_NO to u201801u2019.
Set same PCKG_NO to u20180000000001u2019 in POSERVICES table. Maintain two entries in POSERVICES table like this:
WA_POSERVICES-PCKG_NO = u20180000000001u2019.
WA_POSERVICES-LINE_NO = u20180000000001u2019.
WA_POSERVICES-OUTL_IND = u2018Xu2019.
WA_POSERVICES-SUBPCKG_NO = u20180000000003u2019. (Dummy No.)
WA_POSERVICES-QUANTITY = u2018100.000u2019.
WA_POSERVICES-BASE_UOM = u2018EAu2019.
WA_POSERVICES-PRICE_UNIT = u20181u2019.
WA_POSERVICES-GR_PRICE = u2018100.000u2019.
WA_POSERVICES-SHORT_TEXT = u2018SERVICE TESTu2019.
APPEND WA_POSERVICES TO IT_POSERVICES.
WA_POSERVICES- PCKG_NO = u20180000000003u2019.
WA_POSERVICES- LINE_NO = u20180000000002u2019.
WA_POSERVICES-QUANTITY = u201810.000u2019.
WA_POSERVICES- BASE_UOM = u2018EAu2019.
WA_POSERVICES--PRICE_UNIT = u20181u2019.
WA_POSERVICES-GR_PRICE = u2018100.000u2019.
WA_POSERVICES-SHORT_TEXT = u2018SERVICE 1u2019.
WA_POSERVICES-MATL_GROUP = u20180012u2019.
APPEND WA_POSERVICES TO IT_POSERVICES.
Set PCKG_NO as SUB_PCKG_NO in table POSRVACCESSVALUES this:
WA_POSRVACCESSVALUES-PCKG_NO = u20180000000003u2019.
WA_POSRVACCESSVALUES-LINE_NO = u20180000000002u2019.
WA_POSRVACCESSVALUES-SERNO_LINE = u201801u2019.
WA_POSRVACCESSVALUES-SERIAL_NO = u201801u2019.
WA_POSRVACCESSVALUES-QUANTITY = u201910.000u2019.
APPEND WA_POSRVACCESSVALUES TO IT_ POSRVACCESSVALUES.
This logic will work definitely and PO Service Items will be created.

Acc.assignment object replaced by current master cost center for employee

Hi,
I am facing a peculiar warning message while running the payroll posting run for only 2 employees. The warning message s as follows:
"Acc.assignment object replaced by current master cost center for employee
Message no. 3G399"
Prior to this, there were an error saying the
"Account assignment objects are incorrect. No substitution is possible.
Message no. 3G209"
Later we found that the Position was not assigned to that employee properly. I later assigned the correct position.. but still during the posting run the warning message appears.
Please let me know if this is okay or is this an error which restricts the postings.
Regards,
Balaji TR

Your postings will go through with the first warning message. However, please be warned that any account assignment related entries (IT 0027, 2001, 2002) will be wholly ignored.
Check if any entries have been made to different cost centers for the erroring employees. If so, check for the reason why those entries have been made (since it is evident that the configuration does not support such entries). You may need to tie in with a CO consultant to ensure that there are no loose ends.

Acc assignment vs determination

hi,
1) acc assignment - can be in anywhere of various modules, fi, co, mm, fd. during data entry, we need to MANUALLY put in the gl account in acc assignment fields. right?
2) acc determination - define in obyc or vkoa. this will let the system to determine which transaction code like bsx, wrx to use depends on which business process. this is more to BACKEND defined as compare to account assignment. right?
3) what is the main difference of assignment and determination? can i say assignment only single gl account whereas determination will be the double entry.
hope to have clarification.
thanks

hi,
point given to all.
clarify the following reply.
in acct determination too you can single entry for acct determination if you dont select in the rules debit or credit.
1)what does it mean do not select in the rules debit or credit?
2) in obyc or vkoa i notice some without gl account but some with gl account. what does it mean?
In a sales transaction the cutomer is debited and the revenue account is credited. Here the sales account is determined via VKOA, as you rightly said. This is becuse of 'account determination'. However, only one of the entry is determined, the corresponding debit entry, namely customer account is not known until you do the sale.
We cannot classify strictly that 'Account Determination' will provide all theG/L accounts for the completion of journal entry. The other way is true.
3) how the system determine the sales account? i mean how can system know which sales acc to credit? do we need to enter any thing so system will know which sales account to use? any example?
4) 'the other way is true' - what does it mean?
thanks

Prevent of using limit order with certain acc. assignment category

We have in total 4 different account assigment categories. One of them (Asset with GR - Y in the backend) we do not want it to be used in combination with a limit order.
So in the backend we did NOT maintain the combination between item category B and acc. assign cat Y.
But users then still can make the PO which will end up in error "Combination item category B/acc. assignment Y not defined" , as stated before this is OK want we would expect.
But is there any way to even prevent the user to make in SRM a limit order with acc assigment cat Asset / Y

thx,
so we need to build a custom check. It is not like in backend you can configure which combinations are valid .
Martijn

GL Account & PRCTR to be populated automatically for Acc Assigned PO.

Hello SAP Gurus,
I have a scenario in which the GL Account is not automatically getting populated for acc assigned PO with acc assignment category 'Y'
We are using the acc assignment Y for NRE material type as a service charge.
We have maintained the acc modifier as ZAX and the same was assigned to a GL acc in Configure automatic posting - OBYC for GBB(offsetting inventory posting). We have only one acc for this type of charges.
We are in ECC 6.0 version where we are having this issue.
However the same is working fine in current production system which is in 3.1i
Also the PRCTR is not getting populated automatically but the material is created with a PRCTR.
Request your immediate help on the same.
Thanks for the support.
Best Regards,
Narayana Rao.

Hi
have you maintained the valuation class in the Configuration of GBB - ZAX.
As your settings seems right only.
thanks & Regards
Kishore

Making acc assignment group mandatory in material master sales view

hi,
could someone help me how to make acc assignment group (sales org:2)in material master mandatory.just acc assignment group not other fields which comes along with it . thanks
kulandaivel

Hi,
For making any field in material master optional/mandatory/hide , follow the steps:
1.Just click the tab ,(Which is u want to be mandatory)and get the field name
2.Go to T.Code: OMSR and enter that field name and get Selection Group
3.1. Use t.Code: OMS2 and click your material type and in next screen check Field reference ( you have assigned for material type){{ ( example :;For ROH material type the Field reference is ROH)
3.2. use T.code:OMS9,, Double Click your Field Reference and select field selection Group & select round box of mandatory and save
Regards,
Biju K

Configure Acc Assign Cat K for Company Code Specific

Hi Gurus,
Is it possible to configure acc assignment category K Company Code Specific? Actually I configured the acc assignment category K in OME9 and set indicator assign scr = 2 (multi acc assign is active) now my client has 7 group companies. Client needs multiple account assignment for only one company code. How do I modify the category K for one company code only?
Is there any way I can do it by User Exit? If so please tell me the procedure.

Is it possible to configure acc assignment category K Company Code Specific? Actually I configured the acc assignment category K in OME9 and set indicator assign scr = 2 (multi acc assign is active) now my client has 7 group companies. Client needs multiple account assignment for only one company code. How do I modify the category K for one company code only?
HI,
There is no direct assignment in between Cost center and company code. But cost centers are created under profit center of company code and the Profit center is assigned with specific company code. If you create Cost center then system will ask you to enter Profit center which is link with company code.
Take help from your FI Guys they will create cost center as you required.

New Acc assignment

Dear all,
I have created new account assignment category and have maintained new Acct modification (HAP) and have done the setting in OBYC, [0001 - HAP - Z002 - GL 20015 , 20015], in addition i have created new non vaulted material and new val class i have assigned the Acc Ref to Valuation class, then material type to Val Class.
now when ever i create PR with Acc assignment for the new one system doesn't propose any value. is there any additional Config i m missing

solved

PSM-FM-Reversal of funds management document after change in acc.assignment

Good day we recently went live with a component of Funds Management i.e. Availability Control on Cost centers and cost elements. We update BCS with the plan values and actual/commitment items in Finance/CO. We do our planning in CO.
The solution is working reasonably well but we have encountered a problem for which we are unable to find a solution. The problem is best illustrated with an example;
1. Create purchase requisition with Account Assignment Category "K" = Cost Center with transaction ME51N
2. Account assignment = cost center and cost element. A funds management document is created upon saving of the transaction.
3. Purchase Req. is released with a release strategy (transaction ME54N)
4. After purchase requisition release the account assignment for the cost element is changed by the user. This occurs sometimes during the execution of the business process.
5. When a purchase order is created with reference to this purchase requisition with transaction ME59N the system references the original funds management document which means when the account assignment was changed the funds management document was not reversed and a new funds management document created for the changed account assignment.
6. The BUDCON report transaction FMRP_RW_BUDCON thus displays the commitment under the incorrect commitment item as the change in account assignment is not reflected in Funds Management. We have a one to one relationship between cost elements/commitment items and cost centers/funds centers as per the derivation strategy.
My question is;
Is this normal standard SAP standard behavior or are we missing some configuration that will enable the creation of a new funds management document and if so where do we configure such? I must mention our solution is completely SAP standard.
Thank you in advance.
Best Regards
Mike Olwagen
Manager SAP Solution Support
City Power (JHB) (Pty) Ltd

Hi Mike, nice to meet you.
I think u should do an entire test with TRACE on, and u will find the problem, and how to fix it (at FMDERIVE of course).
First: Have a look at note [666322|https://service.sap.com/sap/support/notes/666322], go to FMDERIVE and turn ON the trace.
Then, run all the process ... from ME51N to the end...
I agree with Eli, u must allow overwriting of existing values at FMDERIVE rule...
Regards,
Osvaldo.

Assign release to document type

I have made release startegy for PR and PO . I want to now assign it to document type . What is the menu path.

Hi,
Go to CL24N
and select you release strtagy and here based on your Release stretagy settings like Class,characters and release code assign Document Type for the required characteristics
check it you will get it
with regards
Shrinivas gangoor

No possibility to show field "Aux acc. assignment 1" in transaction KSB1

Hello together,
we have a strange effect in our R/3-systems.
When call transaction KSB1, we expect to show nearly all fields of the cost center line item.
Especially we want to choose the fields "Auxiliary account assignment 1" in the concerning Display variant.
We have the effect that for some users the field is offered when changing the display variant.
But for some users the field is not offered.
Do you know why there are different fields offered to chose for the display variant (in trx KSB1) ?
Kind regards
Udo

I forgot to tell you that we are using SAP R/3 Release 4.6B.
Kind regards
Udo

Acc Assignment Release

Similar Messages

Maybe you are looking for