on 06-04-2008 11:40 AM
Hello,
in which table are the vendors stored in SRM? How can I find out the corresponding vendor number in the backend from SRM itself ?
The SC that has been aprroved and is stuck in trasfer because the vendor currency is maintned in the backend but not in the SRM.
Now the vendor cuurency is maintined(vendor updated) in the SRM but still the SC is stuck though i try to resubmit it? It gives error as ME083 enter order type(ie. error from backend)
Could you please provide inputs?
Regards
Sachin
Can't you use the 'Manage Business Partner' transaction within SRM to find this?
You could also use gui transaction BP...
Keith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Keith,
I got the vendor guid via bbp_pd and used it to get the number (in backend)of the vendor from Vendmap.
Could you please guide me as where the vendor currency is maintained/replicated in SRM(for Comp code&purch org combination) and the later part fo the question of SC being stuck ?
regards'
Sachin
Hello Sachin,
SRM vendor table is VENMAP.
Concerning your error message, if it is a R/3 one, try to create directly your PO type in the backend: it will be easier for you to debug and see what takes place.
Regards.
Laurent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sachin,
When replicatng the vendors from R/3 to SRM,if you have kept the same no (as R/3) then you can see these vendor nos and the corresponding BP guid's in SRM in the table "VENMAP".
Reg your error,can you check whether attribute BSA - Document type in R/3 system has been assigned for the Use in the Org structurer?
Also see if the foll notes/links are helpful:
Note 798537 - BAPI_PO_CREATE1: ME083, although goods supplier filled
Note 999801 - ME59N: Enter order type
Note 994209 - ME57/ME59N : Wrong document type proposed
Note 852641 - Business Add-In ME_BSART_DET is not always processed
Note 940532 - Error message ME 083 during purchase order generation
Note 1000184 - Account assignment error when document transfer to back end
Note 990946 - BBPSC01: Accounting error during PO creation
Note 980017 - Follow-on document not created
Note 963524 - Determination of a follow-on document for requirements
Note 887308 - Transaction type for text transfer from shopping carts
Note 815849 - FAQ: Account assignment system response
Note 591367 - ME22N Change of document type for stock transfer
Note 663648 - PO_HEADER_ADD_DATA+BADI BBP_PO_CREATE_BACK Error in backend
Note 784556 - No PO for service BID with more than one item
Note 624172 - Purchase order not created due to missing purchasing group
Note 508626 - ME21, ME22: Create asset in multiple account assignment scr.
BR,
Disha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.