Account Assignment WBS not updated in Service PR

Dear Expert
I am creating Service Purchase Requisition from project but in Account Assignment only network is coming , our requirement is WBS as account assignment,
in Account assignment tab WBS field is coming but WBs is not updating,
pls suggest , is there any configuration issue ??
rgds
rkp

I think it is standard .
If you need WBSE then create manual PR with account assignment P.

Similar Messages

Planner group is not updated in service notification using BAPI

Hi,
Planner group is not updated in service notification using BAPI BAPI_ALM_ORDER_MAINTAIN.
I have written the below code, but planner group is not updated in the service notification.
Please advice which parameters do i need to pass to update planner group in the service notification.
          wa_methods-refnumber      = '000001'.
          wa_methods-objecttype     = 'PARTNER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000002'.
          wa_methods-objecttype     = 'HEADER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000000'.
          wa_methods-objecttype     = ' '.
          wa_methods-method         = 'SAVE'.
          APPEND wa_methods TO i_methods.
          REFRESH i_partner.
          CLEAR wa_partner.
          wa_partner-orderid        = wa_subscr1-aufnr.
          wa_partner-partn_role     = 'VW'.
          wa_partner-partn_role_old = ''.
          wa_partner-partner        = wa_subscr1-parnr.
          wa_partner-partner_old    = ''.
          APPEND wa_partner TO i_partner.
          REFRESH i_planrgrp.
          CLEAR wa_planrgrp.
          wa_planrgrp-orderid        = wa_subscr1-aufnr.
          wa_planrgrp-plangroup      = wa_subscr1-ingpr.
          APPEND wa_planrgrp TO i_planrgrp.
          REFRESH i_planrgrp_up.
          CLEAR wa_planrgrp_up.
          wa_planrgrp_up-orderid     = wa_subscr1-aufnr.
          wa_planrgrp_up-plangroup   = 'X'.
          APPEND wa_planrgrp_up TO i_planrgrp_up.
*----Change order details with Technician name
          CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
            TABLES
              it_methods   = i_methods
              it_header    = i_planrgrp
            it_header_up = i_planrgrp_up
              it_partner   = i_partner
              return       = i_return.
Thanks & regards,
Krishna

Try this way
CALL FUNCTION 'BAPI_SERVNOT_CREATE'
EXPORTING
* EXTERNAL_NUMBER =
notif_type = 'S3'
notifheader = ls_notif_h
* TASK_DETERMINATION = ' '
* SENDER =
* ORDERID =
IMPORTING
NOTIFHEADER_EXPORT = ls_notif_e
TABLES
* NOTITEM =
* NOTIFCAUS =
* NOTIFACTV =
* NOTIFTASK =
* NOTIFPARTNR =
* LONGTEXTS =
* KEY_RELATIONSHIPS =
return = lt_return
* IF lt_return IS INITIAL.                                               " <<< Comment this lie
read table lt_return into ls_return with key type = 'E'. " << Change
if sy-subrc ne 0.                                                             " << Change
COMMIT WORK AND WAIT.
write: / ls_notif_e-NOTIF_NO.
ELSE.
LOOP AT lt_return INTO ls_return.
WRITE:/ 'errors'.
* ls_return.
ENDLOOP.
endif.
a®

'BAPI_PO_CREATE1' Multiple account assignment is not possible for AFS item

'BAPI_PO_CREATE1' -> This BAPI works perfectly without the 'account assignment' option . But for purchase requisitions which have account assignments BAPI returns the error - E|8W |185   |Multiple account assignment is not possible for AFS items.
Can somebody please help me to get this error resoleve .
My coding I have done like below.
DATA: pohead TYPE bapimepoheader.
DATA: poheadx TYPE bapimepoheaderx.
CONSTANTS : c_x VALUE 'X'.
DATA: exp_head TYPE bapimepoheader.
DATA: return TYPE TABLE OF bapiret2 WITH HEADER LINE.
DATA: poitem TYPE TABLE OF bapimepoitem WITH HEADER LINE.
DATA: poitemx TYPE TABLE OF bapimepoitemx WITH HEADER LINE.
DATA: posched TYPE TABLE OF bapimeposchedule WITH HEADER LINE.
DATA: poschedx TYPE TABLE OF bapimeposchedulx WITH HEADER LINE.
DATA: POACCOUNT TYPE TABLE OF BAPIMEPOACCOUNT WITH HEADER LINE.
DATA: POACCOUNTX TYPE TABLE OF BAPIMEPOACCOUNTx WITH HEADER LINE.
pohead-comp_code = '1000'.   "IEQ1 plant. "'1000'.
pohead-doc_type   = 'NB'     .
pohead-creat_date = sy-datum   .
pohead-vendor = EKKO-LIFNR. "'0000500004'.
pohead-purch_org = purch_org.
pohead-pur_group = purch_grp.
pohead-langu      = sy-langu   .
pohead-doc_date   = sy-datum.
poheadx-comp_code = c_x.
poheadx-doc_type   = c_x.
poheadx-creat_date = c_x.
poheadx-vendor     = c_x.
poheadx-langu      = c_x.
poheadx-purch_org = c_x.
poheadx-pur_group = c_x.
poheadx-doc_date   = c_x.
poitem-po_item    = iLineItem.      "1.
poitem-material   = req_item-MATERIAL.   " '000000000040000234'.
poitem-plant      = req_item-PLANT.
poitem-quantity   = req_item-QUANTITY.
poitem-net_price = NET_PRICE.
poitem-price_unit = PRICE_UNIT.
poitem-shipping   = 'Z1'.
poitem-preq_no    = req_item-PREQ_NO.
poitem-preq_item = req_item-PREQ_ITEM.
poitem-acctasscat = 'K'.
APPEND poitem.
poitemx-po_item    = iLineItem. "1.
poitemx-po_itemx   = c_x.
poitemx-material   = c_x.
poitemx-plant      = c_x .
poitemx-quantity   = c_x .
poitemx-tax_code   = c_x .
poitemx-item_cat   = c_x .
poitemx-acctasscat = c_x .
poitemx-net_price = c_x.
poitemx-price_unit = c_x.
poitemx-shipping   = c_x.
poitemx-preq_no    = c_x.
poitemx-preq_item = c_x.
poitemx-acctasscat = c_x.
APPEND poitemx.
POACCOUNT-PO_ITEM = iLineItem.
POACCOUNT-SERIAL_NO = iLineItem.
POACCOUNT-GL_ACCOUNT = '0000211010'.
POACCOUNT-SD_DOC = '0001001056'.
POACCOUNT-ITM_NUMBER = '000100'.
POACCOUNT-CO_AREA = '1000'.
APPEND POACCOUNT.
POACCOUNTX-PO_ITEM = '00001'.
POACCOUNTX-SERIAL_NO = '01'." '01'.
POACCOUNTX-PO_ITEMX = 'X'.
POACCOUNTX-SERIAL_NOX = 'X'.
POACCOUNTX-GL_ACCOUNT = 'X'.
POACCOUNTX-SD_DOC = 'X'.
POACCOUNTX-ITM_NUMBER = 'X'.
APPEND POACCOUNTX.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader = pohead
      poheaderx = poheadx
    IMPORTING
    exppurchaseorder = ex_po_number
    expheader        = exp_head
    TABLES
      return    = return
      poitem    = poitem
      poitemx   = poitemx
      POACCOUNT = POACCOUNT
      POACCOUNTX = POACCOUNTX.

I found the answer

IN SALES ORDER PLANT IS CHANGED BUT FM ACCOUNT ASSIGNMENT IS NOT CHANGED

HI ALL
while changing the plant in sales order LINE ITEM FM accounting assignment is not changing accordingly FOR THE PARTICULAR LINE ITEM.
FOR THIS REASON NO ACCOUNTING DOCUMENT IS GENERATING.
THANKS & REGARDS
MALA

solution found.
Mala k reddy

SRM 7.0 extended : Account assignment is not getting populated by default

Hi All,
We have created Purchase order using shopping cart in SRM 7.0 extended classic scenario. Assuming that the delivery from the vendor is done. In Goods receipt The Account assignment is not getting populated by default. If we did the same manually it is picking up the details by default.
please let me know what we are missing.
Regards,
Lakshmi Narayana

Hi Laksmi
Account info must defaulted if it is not direct procurement.
check or you ordering as direct or not? if you have SC has Acc data and it must be copied into PO by default...
Muthu

Why account assignment is not deleted when push "Order as Direct Material"?

Hi Gurus,
I have a problem with shopping carts (SC) of stock items:
1.- I add 5 items.
2.- I push "Order as Direct Material" button for 3 items only.
3.- I push "Hold" button to set SC with held status.
4.- I modify the SC and push "Order as Direct Material" button for 2 items missing.
5.- I order the SC.
One of the effects that it has the "Order as Direct Material" button is that it deletes the account assignment because the items will use to create a PO stock.
But for the last 2 items (number 4.-) the account assignment is not deleted.
This is causing that the PO's have error: "Invalid tax code".
Somebody can say to me why is not deleting the account assignment for items previously hold?
My systems are:
SRM 4.0 (SRM_SERVER 500) level 8
R/3 4.7 (SAP_APPL 470) level 24

Juan Alonso Valenzuela Rodríguez wrote:
> Hi Gurus,
>
> I have a problem with shopping carts (SC) of stock items:
>
> 1.- I add 5 items. -- O.K - Assumed that you have 5 items added
> 2.- I push "Order as Direct Material" button for 3 items only.O.K.You selected as ORDER as direct only for 3 rd item
> 3.- I push "Hold" button to set SC with held status.- O.K. now HOLD the shopping cart
> 4.- I modify the SC and push "Order as Direct Material" button for 2 items missing.- Now you went to 2 nd items and ORDER as direct
> 5.- I order the SC.but this 2 nd item account data was not removed though you selected as ORDER as direct-
check item data what is stored here DP ? if account assignment not cleared it could be a bug. but you need to convince them to get a correction note.
>
> One of the effects that it has the "Order as Direct Material" button is that it deletes the account assignment because the items will use to create a PO stock.
>
> But for the last 2 items (number 4.-) the account assignment is not deleted.
>
> This is causing that the PO's have error: "Invalid tax code".
>
> Somebody can say to me why is not deleting the account assignment for items previously hold?
>
> My systems are:
> SRM 4.0 (SRM_SERVER 500) level 8
> R/3 4.7 (SAP_APPL 470) level 24

Account Assignment is not populated while creating service PO using BAPI

Hi All,
I am creating a service PO using BAPI_PO_CREATE1 and Its creating PO, But when I go to ME23n and check Account Assignment in Services then Its empty.
Please help me as I am not able to understand what could be the problem...
Thanks & Regards,
Prabhat Pandey

Thanks for your most valuable answer.
Regards,
Prabhat

WBS not updated during MIRO to asset

Dear Gurus
Our task is to post invoice directly to asset using ME21N->MIRO (without delivery) approach and get statistical WBS element commitments and actual values updated.
Commitments (ME21N with AAC "A") are working fine (using statistical cost element 90cat.)
During invoice posting (MIRO) no error generated; asset is capitalized with actual value; WBS element commitments reduced; BUT WBS element actual values not updated.
Configration:
1. Account assignment objects PS_PSP_PNR and PS_PSP_PNR2 activated
2. Acc.assign. objects specified in used depreciation area as "01 APC values posting" Acc.assign. type
Where could be the problem?

I agree, but in our case receipt (MIGO) is organizationally useless. And I don't want to belive this is the source of the problem. But I could be mistaken.
By the way I tried simulate process with MIGO - same issue.

WBS not updated during asset invoice

Dear all,
I post an invoice through MIRO for an asset and i enter a WBS element. However, the line item of the asset is not updated and the WBS element is also not updated with the actual posting.
On the other hand, if i enter an expenses account everything works perfectly.
Any suggestions?

Hi,
Usually you should not assign Cost objects to balance sheet accounts. It has to be assigned only for Profit and Loss accounts.
For assets you can maintain the WBS element in Asset Master creation AS01 and that WBS will be taken for accounting for any depreciation or expenses posted for that particular assets.
thanks and regards
Praveen.J

Assignemnt field (ZUONR) not updating for Service Order RAS

Hello Experts,
I am facing an issue in service order RAS (Order Related Billing), here assignment field (VBRK-ZUONR and BSEG-ZUONR) is not updating against document type RV.
Same is not reflected against customer in FBL5N also.
Please suggest.
Regards
Rajat

Hi
Check the copy rules in tcode VTFL and/or VTFA. Check the field for assignment number. Check also the VOFM subroutines.
Also, check Note 301077 - User exits for the interface to accounting to change the value of ZUONR in BSEG (in ACCIT in the interface of this FM)
Regards
Eduardo

Multiple Account Assignment issue with BAPI_PO_CREATE1 for service POs

Whle creating service PO through BAPI_PO_CREATE1, The account assignments at the service line items were not being added correctly at the item level, instead they are getting split further wrt tax jurisdiction. This is occuring when an item have multiple service line items with mutltiple account assignments.
The sample code is below, and the all the internal tables and structure were related to BAPI_PO_CREATE1. Tried with BADI ME_TAX_FROM_ADDRESS and User Exit enhancement SAPL2012, which were not helpful for this particular scenario.
Item Details
W_BAPI_ITEM-PO_ITEM = 1.
W_BAPI_ITEMX-PO_ITEM = 1.
W_BAPI_ITEM-ITEM_CAT = D.
W_BAPI_ITEMX-ITEM_CAT = 'X'.
W_BAPI_ITEM-ACCTASSCAT = K.
W_BAPI_ITEMX-ACCTASSCAT = 'X'.
W_BAPI_ITEM-PLANT = USMP. Tax Jurisdiction code 3604931001
W_BAPI_ITEMX-PLANT = 'X'.
W_BAPI_ITEM-MATL_GROUP = IT37.
W_BAPI_ITEMX-MATL_GROUP = 'X'.
W_BAPI_ITEM-QUANTITY = 1.
W_BAPI_ITEMX-QUANTITY = 'X'.
W_BAPI_ITEM-PRICE_UNIT = 1.
W_BAPI_ITEMX-PRICE_UNIT = 'X'.
W_BAPI_ITEM-PO_UNIT = LE.
W_BAPI_ITEMX-PO_UNIT = 'X'.
W_BAPI_ITEM-NET_PRICE = 100.
W_BAPI_ITEMX-NET_PRICE = 'X'.
W_BAPI_ITEM-PCKG_NO = 3456.
W_BAPI_ITEMX-PCKG_NO = 'X'.
W_BAPI_ITEM-PREQ_NAME = RTPTS02.
W_BAPI_ITEMX-PREQ_NAME = 'X'.
APPEND W_BAPI_ITEM TO IT_BAPI_ITEM.
APPEND W_BAPI_ITEMX TO IT_BAPI_ITEMX.
Delivery address details - Tax Jurisdiction 3305923401
W_BAPI_ADDRDEL-PO_ITEM = 1.
W_BAPI_ADDRDEL-NAME = COR.
W_BAPI_ADDRDEL-NAME_2 = Chairman.
W_BAPI_ADDRDEL-BUILD_LONG = 1001R
W_BAPI_ADDRDEL-CITY = plainview.
W_BAPI_ADDRDEL-STREET = old country road.
W_BAPI_ADDRDEL-POSTL_COD1 = 11803.
W_BAPI_ADDRDEL-COUNTRY = US.
W_BAPI_ADDRDEL-REGION = NY.
APPEND W_BAPI_ADDRDEL TO IT_BAPI_ADDRDEL.
First Account Assignment - 3310300441
W_BAPI_POACNT-SERIAL_NO = 1.
W_BAPI_POACNTX-SERIAL_NO = 1.
W_BAPI_POACNTX-SERIAL_NOX = 'X'.
W_BAPI_POACNT-CREAT_DATE = 11/03/2010.
W_BAPI_POACNTX-CREAT_DATE = 'X'.
W_BAPI_POACNT-QUANTITY = 0.75.
W_BAPI_POACNTX-QUANTITY = 'X'.
W_BAPI_POACNT-DISTR_PERC = 75.
W_BAPI_POACNTX-DISTR_PERC = 'X'.
W_BAPI_POACNT-NET_VALUE = 75 .
W_BAPI_POACNTX-NET_VALUE = 'X'.
W_BAPI_POACNT-PO_ITEM = 1.
W_BAPI_POACNTX-PO_ITEM = 1.
W_BAPI_POACNTX-PO_ITEMX = 'X'.
W_BAPI_POACNT-GL_ACCOUNT = 641099.
W_BAPI_POACNTX-GL_ACCOUNT = 'X'.
W_BAPI_POACNT-COSTCENTER = 10010394.
W_BAPI_POACNTX-COSTCENTER = 'X'.
W_BAPI_POACNT-CO_AREA = 1234.
W_BAPI_POACNTX-CO_AREA = 'X'.
APPEND W_BAPI_POACNT TO IT_BAPI_POACNT.
APPEND W_BAPI_POACNTX TO IT_BAPI_POACNTX.
Second Account Assignment
W_BAPI_POACNT-SERIAL_NO = 2.
W_BAPI_POACNTX-SERIAL_NO = 2.
W_BAPI_POACNTX-SERIAL_NOX = 'X'.
W_BAPI_POACNT-CREAT_DATE = 11/03/2010.
W_BAPI_POACNTX-CREAT_DATE = 'X'.
W_BAPI_POACNT-QUANTITY = 0.25.
W_BAPI_POACNTX-QUANTITY = 'X'.
W_BAPI_POACNT-DISTR_PERC = 25.
W_BAPI_POACNTX-DISTR_PERC = 'X'.
W_BAPI_POACNT-NET_VALUE = 25 .
W_BAPI_POACNTX-NET_VALUE = 'X'.
W_BAPI_POACNT-PO_ITEM = 1.
W_BAPI_POACNTX-PO_ITEM = 1.
W_BAPI_POACNTX-PO_ITEMX = 'X'.
W_BAPI_POACNT-GL_ACCOUNT = 641099.
W_BAPI_POACNTX-GL_ACCOUNT = 'X'.
W_BAPI_POACNT-COSTCENTER = 10010393.
W_BAPI_POACNTX-COSTCENTER = 'X'.
W_BAPI_POACNT-CO_AREA = 1234.
W_BAPI_POACNTX-CO_AREA = 'X'.
APPEND W_BAPI_POACNT TO IT_BAPI_POACNT.
APPEND W_BAPI_POACNTX TO IT_BAPI_POACNTX.
Service Item detials
W_BAPI_SERVICE-OUTL_IND = 'X'.
W_BAPI_SERVICE-SUBPCKG_NO = 3457.
W_BAPI_SERVICE-LINE_NO = 1.
W_BAPI_SERVICE-PCKG_NO = 3456.
W_BAPI_SERVICE-EXT_LINE = 0000000000.
W_BAPI_SERVICE-QUANTITY = 0.
W_BAPI_SERVICE-BASE_UOM = 0.
W_BAPI_SERVICE-PRICE_UNIT = 0.
W_BAPI_SERVICE-GR_PRICE = 0.
W_BAPI_SERVICE-SHORT_TEXT = 0.
W_BAPI_SERVICE-MATL_GROUP = 0.
W_BAPI_SERVICE-DISTRIB = 0.
APPEND W_BAPI_SERVICE TO IT_BAPI_SERVICE.
W_BAPI_SERVICE-OUTL_IND = 'X'.
W_BAPI_SERVICE-LINE_NO = 2.
W_BAPI_SERVICE-PCKG_NO = 3457.
W_BAPI_SERVICE-EXT_LINE = 0000000010.
W_BAPI_SERVICE-QUANTITY = 10.
W_BAPI_SERVICE-BASE_UOM = STD.
W_BAPI_SERVICE-PRICE_UNIT = 0.
W_BAPI_SERVICE-GR_PRICE = 5.
W_BAPI_SERVICE-SHORT_TEXT = Cabling Services1.
W_BAPI_SERVICE-MATL_GROUP = IT37.
W_BAPI_SERVICE-DISTRIB = 2.
APPEND W_BAPI_SERVICE TO IT_BAPI_SERVICE.
W_BAPI_SERVICE-OUTL_IND = 'X'.
W_BAPI_SERVICE-LINE_NO = 3.
W_BAPI_SERVICE-PCKG_NO = 3457.
W_BAPI_SERVICE-EXT_LINE = 0000000020.
W_BAPI_SERVICE-QUANTITY = 10.
W_BAPI_SERVICE-BASE_UOM = STD.
W_BAPI_SERVICE-PRICE_UNIT = 0.
W_BAPI_SERVICE-GR_PRICE = 5.
W_BAPI_SERVICE-SHORT_TEXT = Cabling Services2.
W_BAPI_SERVICE-MATL_GROUP = IT37.
W_BAPI_SERVICE-DISTRIB = 2.
APPEND W_BAPI_SERVICE TO IT_BAPI_SERVICE.
Service Account assignment details
W_ACC_SERVICE-PCKG_NO = 3457.
W_ACC_SERVICE-LINE_NO = 2.
W_ACC_SERVICE-SERNO_LINE = 1.
W_ACC_SERVICE-SERIAL_NO = 1.   "Account Assignment Link
W_ACC_SERVICE-NET_VALUE = .
W_ACC_SERVICE-QUANTITY = 50 .
W_ACC_SERVICE-PERCENTAGE = 100 .
APPEND W_ACC_SERVICE TO IT_ACC_SERVICE.
W_ACC_SERVICE-PCKG_NO = 3457.
W_ACC_SERVICE-LINE_NO = 3.
W_ACC_SERVICE-SERNO_LINE = 1.
W_ACC_SERVICE-SERIAL_NO = 1.   "Account Assignment Link
W_ACC_SERVICE-NET_VALUE = .
W_ACC_SERVICE-QUANTITY = 50 .
W_ACC_SERVICE-PERCENTAGE = 50 .
APPEND W_ACC_SERVICE TO IT_ACC_SERVICE.
W_ACC_SERVICE-PCKG_NO = 3457.
W_ACC_SERVICE-LINE_NO = 3.
W_ACC_SERVICE-SERNO_LINE = 1.
W_ACC_SERVICE-SERIAL_NO = 2.   "Account Assignment Link
W_ACC_SERVICE-NET_VALUE = .
W_ACC_SERVICE-QUANTITY = 50 .
W_ACC_SERVICE-PERCENTAGE = 50 .
APPEND W_ACC_SERVICE TO IT_ACC_SERVICE.
EKKN table entries:
When created thru ME21N with the same set of data,which is expected
ZEKKN            MENGE            NETWR SAKTO        KOSTL
01               0.750            75.00 0000641099   0010010394
02               0.250            25.00 0000641099   0010010393
But through BAPI_PO_CREATE1, the below split is being done with respect to Tax Jurisdiction code.
01               0.500            50.00 0000641099   0010010394
02               0.250            25.00 0000641099   0010010394
03               0.250            25.00 0000641099   0010010393
Please advice the solution.
PS: there were different tax jurisdiction codes were being determined.
Plant, Cost Center and Delivery Address.

Hi,
To commit BAPI or to run it properly , you need to fulfill all required data for BAPI.
You can go to BAPI documentation to check for mandetory parameters and also check with Function consultant for more data and confifuration/
Reward if useful!

Block account assignment category in PR with service item category

Hello Gurus!
Is it possible to disble all account assignment category in PR when using service item category in PR? Only leaving "U" as possible option?
I see I do it in customizing under Define Combination of Item Categories/Account Assignment Categories by deleating all the combination but the D-U combination. However, this will affect also the PO documents.
Is there any other option?
Thanks,
Alejandro Es

Hi
I am not sure we can achive this or not check following link ,it has user exit and bapi for PR
[/community [original link is broken] D=649304]
Regards
Kailas Ugale

How to add entries in possible fields in Account assignment model/Note 2596

Hi Friends,
I want to know How to apply OSS Note 2596, The basic requirement is to to add entries in the list of possible fields in Account assignment model( Exactly in program SAPDFKA6 in screen 120).
I found the note 2596 to achieve this, and the field that I want to add is KMZEI-PAOBJNR.
I gone through the note and it is very confusing for me .. If any one knows how to achieve this or how to apply this note, please let me know.
Thanks,
Rk

I got this myself.
Thanks,
Rk

Account assignment category not flowing to PR and PO in MTS

Dear All,
I am facing a problem in MIGO. When I enter the PO number, it says, PO has no selectable items.
When I consulted with MM consultant here he says the Account assignment category is not there in PO. And this has to flow in PR and PO when it is created.
The PR is cretaed by MRP run and the strategy used is 40.
Is this is the reason for error in MIGO? If yes where I do need to set this so that account assignment category will come in PR and hence in PO.
Please suggest.
Sumeet Vaidya

Hi,
Since the PO is not released , it is not allowing you to do MIGO.
Hope , there might be a Release Procedure / Release Strategy defined for the Purchase Order. So pls consult with your MM Consultant and get the PO released.
Then you will able to post the Goods Movements.
Regards,
Sheik
Edited by: sheik abdulla on Apr 17, 2008 6:00 PM

COPA - Account assignment is not green in Credit memo Request

For regular sales orders ( not credit memo reqs), acct assignment is turning green, but not for credit memo reqs. when I get into account assignment and hit continue it turns green. When a credit memo is created (VF01), acct assignment / characteristics are all getting posted normally into COPA.
I don't have value flow from Sales order active in config, if this is the reason even for normal sales order it shouldn't turn green. Whats wrong with cr memo reqs? any ideas ?
Thanks
Chris

As already suggested, go to OVA2, Select "B - Sales item", Double click on Procedures, Select "20 - Standard item", Double click on "Fields" and finally maintain the following:-
Table Fldname Description Scr. Status
VBAP PAOBJNR Profitab. Segmt No. PKNT 01
Now try the process
thanks
G. Lakshmipathi

Account Assignment WBS not updated in Service PR

Similar Messages

Maybe you are looking for