Vendor payment and customer recipts across company codes

Hi all,
We are having 4 company codes in US.The vendors and customers are spread across company codes.
1st scenario:
Vendor "abc" has a debit balance os 5000 in company code A. In company code B, the same vendor has credit balance of 10000.
How can we net the balances in both compnay codes and pay the difference to the vendor. The client has separate house banks for each company code.
2 nd scenario:
A customer sends a check for 2500. which needs to be applied against company code A (500) and Company code B (2000)
How does the payment and receipts needs to be applied across company codes. Kindly suggest.
Regards,
Amulya.
Edited by: amulya chowdary on May 21, 2010 4:31 PM

Hi,
You need to configure cross company clearing thru OBYA.
Your queries can be addressed either treating other company code as the vendor/customer or clearing to a inter company GL.
Best Regards,
Madhu

Similar Messages

Possible to parking payment entry ( Ex.vendor payment and customer payment)

Hi Masters
Are you possible to parking payment entry , payment paid to vendor and payment received from customer if there any configuration or guide me how to parking payments.
Regards
Selva

Hi Javeed,
I thought wrongly you understand my question, Normally parking for sales invoice (T.code: F-22 Or FB70) purchase invoice (T.Code.F-43 Or FB60), General expenses entry (T.code: F-02). Normally the above documents park T.Code: FBV0,
my question is payment paid to vendor (T.Code: F-53) and payment received from customer (T.code: F-28), payment entry we can possible to parking.
If possible what T.code? or any configuration there tell me.
Thanks & regards
Selva.

Extend customer to multiple company codes and mutliple sales organisations

Hi,
Customers with only general info. are getting created from CRM system to SAP ECC. Now we extend the same customer to differnt company codes and different sales organisations.
When I checked the BADI, CUSTOMER ADDDATA, in this S_KNA1, S_KNB1, S_KNVV structures are there only. So is it possible to extend it to mutiple company codes at the same time.
It is mostly appreciated for early response.
Thanks,

Hi,
You can use fm SD_CUSTOMER_MAINTAIN_ALL to extend customer to sales are and company code.
Using this fm you can maintain all customer master data.

Transporttaion Cross Docking between EWM and ECC across company codes

Seceanrio is as follows:
We have an EWM managed site in GB, and an IM managed site in IE.
We would like to use the transportation cross docking solution from within Service Parts Management to transfer goods from GB to IE, (ECC > EWM > ECC) across company codes.
Is this possible within the standard SAP solution?
Thanks in advance,
Craig Bramhald

Hi Hari
Inter Company Purchase scenario works when the same material exists in both the company codes... I dont know how SAP would manage this in the case of Assets, when the Same Asset No is not existent in the other Co Code...
However, Refer 1523976 PurchaseOrderERPRequest_In_V1:Asset account assignment fails
This applies to EhP4 / EhP5 - But I dont know if you are using the enterprise service PurchaseOrderERPRequest_In_V1 ....
If not, better create an OSS message to SAP and check with them mentioning the notes that you have mentioned in your message
BR,Ajay M

Posting across Company Codes

Can someone please suggest the most efficient of posting Customer and Vendor transactions across different company codes.
We are beginning to receive customer payments into a bank account and company code (DP01) that is different from the Customer's original company code transaction (HA01). Similarly, we are making payments to vendors in DP01 whose original invoice has been entered into HA01.
There are already intercompany reconcilation accounts between the various company codes, but, I am after the most efficient way of posting for example, Debit bank clearing in DP01, Credit Customer in HA01, and, credit Bank clearing in DP01, debit Vendor account in HA01.
Thanks and regards,
RB

I believe the best way to handle inter-company cash management type transaction through the standard SAP FI inter-company posting of AR and AP balances. I would recommend to use G/L account as inter-company receivables and payables account.Also, you probably don't want manual transaction to those inter-company receivables and payables. Now, it probably will be outside the scope of a forum post to detail everything about it. At least you have some clues here.

Double Invoice check across company code

Hi All,
I have been trying to use the double invoice check functionality across company codes. i.e. when an invoice is posted in Company code A with ref no: xxx, and when I try to post a new inovice with the same reference ie. xxx in company code B, system does not give error message.
Please note: I have maintained message in application F5, no: 117 and 312.
Also in customization for double invoice check, I have unchecked "Check Company code" and checked "check reference" and "check invoice date"
I have also maintained the double invoice check flag in the vendor master.
Please help at the earliest.
Regards,
Ankush

Hi Ankush,
Good Day,
Duplicate invoice check across company code will not check for FI related invoice ( Like FB60)
But you can able to achive this with BTE ( SAMPLE_PROCESS_00001110 for FI Duplicate invoice check)
Steps for Implementing a BTE
(1)Goto transction FIBF menu Environment->Info System (P/S )
(2)Select the BTE you want to implement.
(3)Press button Sample function module
(4)This brings you to SE37 - Copy the sample function module to a Z-function module (First create a new function group for the function module) . Note: The name of the Z-functionmodule is not important
(5)Edit the code in the new function module
(6)Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a new product whicj identifies the new product . Remember to mark the Active field.
(7)Go back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that links the BTE and Product with the new function module
Best Regards,
KSK

Vendor Master and Customer Master for FI AP/AR

hi FICO Gurus,
I am Sapna here and I have questions regarding the Mandatory fields for Vendor Master and Customer Master which would be mandatory for Running FI AP and AR. I am basically a MM Consultant but I have been asked to perform this role of Master Data at my current client.
I am quite familiar with the fact that these feilds are based on the needs of the bussiness and can be configured in IMG as required/optional or suppressed or diaplsy only.
What I am looking is
1. Are there any fileds list which is Mandatory for running FI AP/AR in global financial implemntation.
2. Also from FI Perspective what is Good to have/Recommended fields in Vendor Master and Cusotmer Master for Global Finacial implemtation.
Your help is greatly appreciated. Please point me in right direction...

OK all implementations are different so the client should have some imput here.
However you need to make sure certain address details are mandatory such as name, post code street and city.
You may always want an e mail address or phone number.
All AR & AP customer/ Vendors will need a recon account, so it is important there is one set up, but you also need to make sure in change mode this cannot be changed.
For Vendors you will require some kind of bank details and payment method.
For Customers if Dunning is being used you may need the Dunning Procedure and Accounting Clerk.
Also for a Customer there is the Sales Org view, and it is best to contact the SD consultant to see which fields are required here. The tax code, payment terms are normally mandatory.
For the Purchasing Org, I guess you would know about this...
Hope this helps.
Award points if useful.

RFIDYYWT across company codes produces 1099 with multiple records per TIN

We have multiple company codes that post 1099-MISC relevant payments to a common set of vendors. All payments are processed through our main (paying) company code.
All our company codes are one taxable entity to the federal government, with one TIN. We are required to submit one file to the IRS.
Unfortunately, when we execute RFIDYYWT across company codes we get multiple records per vendor, one for each company code, despite that the vendor has only one TIN.
How may we customize the system so that a single execution of RFIDYYWT provides an IRS compliant file that aggregates common vendor records?
Thank you in advance for your assistance.
Regards,
Otto Baskin
P.S. Iu2019m happy to award points.

Hi
We have similar issue.. It's been long time.. but I thought of asking you.. Did you find solution? If so, can you please share.
Thanks
Srini

Create Customer master across company

I can create Customer master across company which I didn't assign Sales org to.
Ex. I have 2 company code, "1001" and "1002" and I assign Sales org "1001" to company code "1001" but I can create customer master in Sales org "1001" at Company code "1002". How can I solve this problem?? All advises are welcome.

Hi,
One customer can belong to any number of companies. So same customer master can be created for any number of company codes; provided unique combination of company code & sales org is maintained.
A sales organisation is uniquely assigned to a company code.ie: a sales org can belong to only one company code.
Taking your example:
company code 1001 & sales org 1001- assigned. so Sales org 1001 cannot be assigned to 1002 at all. so question of creating customer master for combination company code1002 & sales org 1001 does not even arise.

PO with Vendor that not belong to PO Company Code Header.

Hello MM Gurus,
When I create a PO with Company Code 0001, and the system let me selected a vendor who belongs to company code 0002. I would like to create PO with the same vendor a company code header only.
Any Suggestions please let me know.
Regads,
Hector.

Hello Charlie,
The vendor was just created in one company code(0002), and when I created the PO header data for company code 0001, the system don't send any error.
I really believe that standard system couldn't create PO with different company code. ¿It's possible in the Vendor Master Data, in particular the Purchasing Views, check some box to avoid this situation?
Please let me know,
Regards,
Hector.

Bapi For creation and change for Vendor Master and Customer Master

I am looking for BAPI to create and change Vendor Master and Customer Master which will not take me to standard SAP transaction but will work in the background
Explanation: BAPI to delete material (BAPI_MATERIAL_DELETE) take you to standard SAP screen of T-Code MM06 but BAPI to create material (BAPI_MATERIAL_SAVEDATA) creates material in the background i.e. does not take you to standard SAP screen of T-Code MM01
So in my case (i.e. to create and change Vendor Master and Customer Master ) I want BAPI which would work like BAPI to create material (BAPI_MATERIAL_SAVEDATA)

For general information,to find BAPIs associated with any business object :
Transaction : BAPI - choose alphabetical tab - Find customer - (right side choose - tools - create bapi list and search ) , you will get all the BAPIs associated with this particular business object
Mathews

Help - Error in PR BAPI : Purchasing across company codes is not allowed..

I have written a program to create Purchase Requisition.I am using two BAPIs.In the file i specify the old PR No, New Plant,Purch Group and Purch Org.It is actually a program to create a new PR in a new plant which is a copy of an Old PR in older plant.
Program is below:
I am getting the error Purchasing across company codes is not allowed..
Please Help
*& Report ZMMB_BDC_ME51N_WO
REPORT ZMMB_BDC_ME51N_WO.
INITIALIZATION.
D A T A D E C L A R A T I O N *
TYPES: BEGIN OF TY_TABDATA,
 BANFN TYPE EBAN-BANFN, " Purchase Requistion No
 WERKS TYPE MEREQ3211GRID-WERKS, "Plant
 EKGRP TYPE MEREQ3211GRID-EKGRP, "Purchasing Group
 EKORG TYPE MEREQ3211GRID-EKORG, "Purchasing Organization
 END OF TY_TABDATA.
TYPES: BEGIN OF TY_CHECK,
 BANFN TYPE EBAN-BANFN, " Purchase Requistion No
 BNFPO TYPE EBAN-BNFPO, " Purchase Requistion Item No
 EBAKZ TYPE EBAN-EBAKZ, " PR Closed
 END OF TY_CHECK.
Declaration of the Internal Table & Work Area.
DATA:
 IT_TABDATA TYPE STANDARD TABLE OF TY_TABDATA, " Internal Table for file
 WA_TABDATA TYPE TY_TABDATA.
DATA: IT_ITEM TYPE STANDARD TABLE OF BAPIEBAN ,
 WA_ITEM LIKE LINE OF IT_ITEM,
 IT_ITEM1 TYPE STANDARD TABLE OF BAPIEBANC,
 WA_ITEM1 LIKE LINE OF IT_ITEM1,
 IT_ACCOUNT TYPE STANDARD TABLE OF BAPIEBKN,
 WA_ACCOUNT LIKE LINE OF IT_ACCOUNT,
 IT_PRITEMTEXT TYPE STANDARD TABLE OF BAPIEBANTX,
 WA_PRITEMTEXT LIKE LINE OF IT_PRITEMTEXT,
 IT_SERVICES TYPE STANDARD TABLE OF BAPIESLL ,
 WA_SERVICES LIKE LINE OF IT_SERVICES,
 IT_SERVICES1 TYPE STANDARD TABLE OF BAPIESLLC ,
 WA_SERVICES1 LIKE LINE OF IT_SERVICES1,
 IT_SERVICETEXT TYPE STANDARD TABLE OF BAPIESLLTX,
 WA_SERVICETEXT LIKE LINE OF IT_SERVICETEXT,
 IT_CHECK TYPE STANDARD TABLE OF TY_CHECK,
 WA_CHECK LIKE LINE OF IT_CHECK.
 Global data Declaration
DATA: GV_YEAR(4) TYPE C,
 GV_MNTH(2) TYPE C,
 GV_DATE(2) TYPE C,
 GV_DATUM(8) TYPE C,
 GV_ANS TYPE C,
 W_FILENAME TYPE STRING.
Declaration of the Internal Table with Header Line comprising of the uploaded data.
DATA: BEGIN OF IT_FILE_UPLOAD OCCURS 0.
INCLUDE STRUCTURE ALSMEX_TABLINE. " Rows for Table with Excel Data
DATA: END OF IT_FILE_UPLOAD.
Batch Input Data for a single Transaction.
Message of Call Transaction.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
 MSGTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
S E L E C T I O N - S C R E E N *
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001,
 BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-004.
PARAMETERS: P_FNAME LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK B2,
 END OF BLOCK B1.
E V E N T : AT S E L E C T I O N - S C R E E N *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FNAME.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = 'X'
 CHANGING
 FILE_NAME = P_FNAME.
E V E N T : S T A R T - O F - S E L E C T I O N *
START-OF-SELECTION.
Upload Excel file into Internal Table.
PERFORM UPLOAD_EXCEL_FILE.
IF NOT IT_FILE_UPLOAD IS INITIAL.
Confirm whether you want to proceed with the Upload.
 PERFORM CONFIRM_UPLOAD.
 IF GV_ANS EQ '1'.
Organize the uploaded data into another Internal Table.
 PERFORM ORGANIZE_UPLOADED_DATA.
 PERFORM BAPI_CALL.
 ENDIF.
ELSE.
 LEAVE PROGRAM.
ENDIF.
*& Form UPLOAD_EXCEL_FILE
 text
--> p1 text
<-- p2 text
FORM UPLOAD_EXCEL_FILE .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FNAME
 I_BEGIN_COL = 1
 I_BEGIN_ROW = 4
 I_END_COL = 4
 I_END_ROW = 9999
 TABLES
 INTERN = IT_FILE_UPLOAD
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " UPLOAD_EXCEL_FILE
*& Form CONFIRM_UPLOAD
 text
--> p1 text
<-- p2 text
FORM CONFIRM_UPLOAD .
CALL FUNCTION 'POPUP_TO_CONFIRM'
 EXPORTING
 TITLEBAR = TEXT-002
 TEXT_QUESTION = TEXT-003
 IMPORTING
 ANSWER = GV_ANS
 EXCEPTIONS
 TEXT_NOT_FOUND = 1
 OTHERS = 2.
ENDFORM. " CONFIRM_UPLOAD
*& Form ORGANIZE_UPLOADED_DATA
 text
--> p1 text
<-- p2 text
FORM ORGANIZE_UPLOADED_DATA .
DATA : GV_TOTROW TYPE I, "No of records
 GV_ROW TYPE I,
 LC_CNT(3) TYPE N.
GV_TOTROW = 1.
SORT IT_FILE_UPLOAD BY ROW
 COL.
LOOP AT IT_FILE_UPLOAD.
 GV_TOTROW = IT_FILE_UPLOAD-ROW.
ENDLOOP.
GV_ROW = 1.
WHILE GV_ROW <= GV_TOTROW.
 LOOP AT IT_FILE_UPLOAD WHERE ROW = GV_ROW.
 CASE IT_FILE_UPLOAD-COL.
 WHEN '0001'.
 WA_TABDATA-BANFN = IT_FILE_UPLOAD-VALUE.
 WHEN '0002'.
 WA_TABDATA-WERKS = IT_FILE_UPLOAD-VALUE.
 WHEN '0003'.
 WA_TABDATA-EKGRP = IT_FILE_UPLOAD-VALUE.
 WHEN '0004'.
 WA_TABDATA-EKORG = IT_FILE_UPLOAD-VALUE.
 ENDCASE.
 ENDLOOP.
 GV_ROW = GV_ROW + 1.
 APPEND WA_TABDATA TO IT_TABDATA .
 CLEAR :WA_TABDATA.
ENDWHILE.
ENDFORM. " ORGANIZE_UPLOADED_DATA
*& Form BAPI_CALL
 text
--> p1 text
<-- p2 text
FORM BAPI_CALL .
DATA:ITM_NO(4) TYPE N,LV_PERCENTAGE(3) TYPE N,
 LV_MSG(60),
 IT_RETURN TYPE STANDARD TABLE OF BAPIRETURN,
 WA_RETURN LIKE LINE OF IT_RETURN.
DATA: BEGIN OF WA_RETURN1,
 BANFN TYPE EBAN-BANFN.
INCLUDE TYPE BAPIRETURN.
DATA END OF WA_RETURN1.
DATA:IT_RETURN1 LIKE STANDARD TABLE OF WA_RETURN1.
DESCRIBE TABLE IT_TABDATA LINES ITM_NO.
LOOP AT IT_TABDATA INTO WA_TABDATA.
 CALL FUNCTION 'BAPI_REQUISITION_GETDETAIL'
 EXPORTING
 NUMBER = WA_TABDATA-BANFN
 ACCOUNT_ASSIGNMENT = 'X'
 ITEM_TEXTS = 'X'
 SERVICES = 'X'
 SERVICE_TEXTS = 'X'
 TABLES
 REQUISITION_ITEMS = IT_ITEM
 REQUISITION_ACCOUNT_ASSIGNMENT = IT_ACCOUNT
 REQUISITION_TEXT = IT_PRITEMTEXT
REQUISITION_LIMITS =
REQUISITION_CONTRACT_LIMITS =
 REQUISITION_SERVICES = IT_SERVICES
 REQUISITION_SERVICES_TEXTS = IT_SERVICETEXT
REQUISITION_SRV_ACCASS_VALUES =
RETURN =
 COMPUTE LV_PERCENTAGE = ( ITM_NO / SY-TABIX ) * 100.
 CONCATENATE 'PROCESSING PURCHASING REQUISITION FOR OLD PR NUMBER ' WA_TABDATA-BANFN INTO LV_MSG.
 CALL FUNCTION 'RM_SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
 PERCENTAGE = LV_PERCENTAGE
 TEXT = LV_MSG.
 CLEAR:LV_PERCENTAGE ,LV_MSG.
 IF IT_TABDATA[] IS NOT INITIAL.
 SELECT BANFN BNFPO EBAKZ FROM EBAN INTO TABLE IT_CHECK FOR ALL ENTRIES IN IT_TABDATA
 WHERE BANFN = IT_TABDATA-BANFN AND EBAKZ = 'X'.
 ENDIF.
 LOOP AT IT_CHECK INTO WA_CHECK.
 LOOP AT IT_ITEM INTO WA_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
 DELETE IT_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
 ENDLOOP.
 LOOP AT IT_ACCOUNT INTO WA_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
 DELETE IT_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
 ENDLOOP.
 ENDLOOP.
 LOOP AT IT_ITEM INTO WA_ITEM.
 WA_ITEM-PLANT = WA_TABDATA-WERKS.
 WA_ITEM-PUR_GROUP = WA_TABDATA-EKGRP.
 WA_ITEM-PURCH_ORG = WA_TABDATA-EKORG.
 MODIFY IT_ITEM FROM WA_ITEM TRANSPORTING PLANT PUR_GROUP PURCH_ORG.
 MOVE-CORRESPONDING WA_ITEM TO WA_ITEM1.
 WA_ITEM1-PREQ_NO = ''.
 WA_ITEM1-STORE_LOC = ''.
 APPEND WA_ITEM1 TO IT_ITEM1.
 CLEAR WA_ITEM1.
 ENDLOOP.
 LOOP AT IT_ACCOUNT INTO WA_ACCOUNT.
 WA_ACCOUNT-PREQ_NO = ''.
 MODIFY IT_ACCOUNT FROM WA_ACCOUNT TRANSPORTING PREQ_NO.
 ENDLOOP.
 LOOP AT IT_SERVICES INTO WA_SERVICES.
 MOVE-CORRESPONDING WA_SERVICES TO WA_SERVICES1.
 APPEND WA_SERVICES1 TO IT_SERVICES1.
 CLEAR WA_SERVICES1.
 ENDLOOP.
 CALL FUNCTION 'BAPI_REQUISITION_CREATE'
 EXPORTING
 SKIP_ITEMS_WITH_ERROR =
 AUTOMATIC_SOURCE = 'X'
 IMPORTING
 NUMBER =
 TABLES
 REQUISITION_ITEMS = IT_ITEM1
 REQUISITION_ACCOUNT_ASSIGNMENT = IT_ACCOUNT
 REQUISITION_ITEM_TEXT = IT_PRITEMTEXT
 REQUISITION_LIMITS =
 REQUISITION_CONTRACT_LIMITS =
 REQUISITION_SERVICES = IT_SERVICES1
 REQUISITION_SRV_ACCASS_VALUES =
 RETURN = IT_RETURN
 REQUISITION_SERVICES_TEXT = IT_SERVICETEXT
 REQUISITION_ADDRDELIVERY =
 EXTENSIONIN =
 READ TABLE IT_RETURN INTO WA_RETURN INDEX 1.
 IF WA_RETURN-TYPE = 'E'.
 CLEAR WA_RETURN.
 LOOP AT IT_RETURN INTO WA_RETURN WHERE TYPE EQ 'E'.
 WA_RETURN1-BANFN = WA_TABDATA-BANFN.
 MOVE-CORRESPONDING WA_RETURN TO WA_RETURN1.
 APPEND WA_RETURN1 TO IT_RETURN1.
 CLEAR WA_RETURN1.
 ENDLOOP.
 ELSE.
 WA_RETURN1-BANFN = WA_TABDATA-BANFN.
 MOVE-CORRESPONDING WA_RETURN TO WA_RETURN1.
 APPEND WA_RETURN1 TO IT_RETURN1.
 CLEAR WA_RETURN1.
 ENDIF.
 IF SY-SUBRC <> 0.
 ENDIF.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT =
 IMPORTING
 RETURN =
 REFRESH: IT_RETURN[],IT_ITEM[],IT_ACCOUNT[],IT_PRITEMTEXT[],IT_ITEM1[],IT_SERVICES[],IT_SERVICES1[],
 IT_SERVICETEXT[].
ENDLOOP.
WRITE :10 'OLD PR NUMBER' COLOR COL_KEY, 25 'MESSAGE' COLOR COL_KEY.
LOOP AT IT_RETURN1 INTO WA_RETURN1.
 WRITE:/10 WA_RETURN1-BANFN,25 WA_RETURN1-MESSAGE.
ENDLOOP.
CLEAR:IT_TABDATA[],WA_TABDATA.
ENDFORM . "BAPI_CALL

Solved on Own

Control message "Purchase across Company codes is not allowed"

Hello Gurus
We are running SRM5.0 ECS using EP. If we attempt to create a SC that falls foul of the above validation, we get a message but only as a warning. Naturally if a warning, users will ignore and continue the purchasing process up to the point that the PO is created. However, when the PO is transferred to the ECC, we get the "Error in Process" status for the same message, but ECC validation routines have this set to an error and not a warning. Evidently there is a discrepancy with severity between SRM and ECC. We want to ensure that SRM matches up to ECC so it is an error in SRM and not a warning.
Searching the web, I see that the message id is KI-113. Can't be sure this is correct as the portal we use does not display the msg id. I've checked the message control config in SRM, and see nothing for the message. Further investigation reveals that in order to control messages through the config, you can only maintain those that are listed in BBPV_PDMSG. After searching for id or text, I still cannot see how I can escalate ths message to an error.
Any ideas?
Thanks
Ian

Hi peggy
This message comes from your r/3 backend system. go to se91 KI - message no. 113 in sap r/3.
it is not srm message.
Error : Purchasing across company codes is not allowed
BR
Muthu
Edited by: Muthuraman Govindasamy on Oct 13, 2008 10:17 AM

Vendor if not maintained at the company code level

Hi,
System should not save the PO, if the vendor has not maintained at the company code level. How to achieve this?
Regards,
Sattuj

> System should not save the PO, if the vendor has not maintained at the company code level. How to achieve this?
Vendor Need not to be Maintained at Company Code Level For Creating Purchase Order.
During IR only System will Look whether Vendor is Maintained at Company code Level.
Try the User Exit MM06E010 Field selection for vendor address and Check any Possibility is there.
What you can do is you Can Restrict Users to Use MK01. And give Authorization to Limited Users for XK01.
Regards,
Ashok
Edited by: Ashok Kumar Telikula on Sep 18, 2008 9:05 AM

Extend Customer to Different Company code?

Hi.
How to extend Customer to Different Company code?
ie, Cust1 is created with ABC company code, now i want to extend the same with XYZ company code.
in same client.
Reg,
Antaa21

Hi,
In T.Code XD01 - Select relevant account group and enter new company code.
Under reference option enter the existing customer number and sales org details click on continue button enter name and address details remaining information will be copied from existing customer and save.
Thanks,
Padmaja

Vendor payment and customer recipts across company codes

Similar Messages

Maybe you are looking for