Partner determination in control record for EDI

Hi all,
I have a custom EDI output which goes into the delivery. However this EDI output is not picking the correct partner.
The sales order with 2 plants would create 2 deliveries. First delivery is created for plant A121 while second delivery is created for plant A710. However, the vendor partner is not picked up correctly for plant A121 in the first delivery. LIkewise the second delivery. When the sales order has same plants, it create 1 delivery. This comes out with correct partner.
My question is: How is the partner determined in EDI control record before the delivery is created ?
In Partner Profile, WE20, there are 3 defined partners (100 LI, 200 LI, 300 LI). For plant A121, the partner would be vendor 200.
Thanks
Joyce

Hi Vinod,
   Thanks for your suggestion. I have condiiton record for this EDI which is plant and it would list the partner. Somehow, it seems the plant is not picked up correctly when there are a few plants in the sales order.   Becasue the partner is not picked up correctly, it seems to affect other output types that are plant-based.
    Initially the all output for EDI works fine. There have been recent changes made to split delivery by plant which is fine Output is one that are having issues.
   Have you any other suggestions ? I will continue to look at the program you suggested.
thank you.\
Joyce
Edited by: Joyce Chan on Mar 17, 2010 8:31 PM

Similar Messages

Changing IDOC Control Record for EDI inbound Orders Creatiion

Hi,
When I try to process the Inbound orders Idocs file through the GENTRAN EDI System.IDOC's were errored out, because of the Partner function was not defined for the Customer ( Legacy ) ( Type KU ) in the SAP.
Is there any user exit/badi/Configuration to change the Legacy Partner(Customer) to the SAP Partner(Customer) mapping and update the IDOC Control record with the SAP Partner. I am calling EDI_DATA_INCOMING Function module and IDOC_INPUT_ORDERS.IDOCs errored out with Message EO-332 ( Partner function not defined ).
Advance Thanks,
Balaji.

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

EA608 EDI: Sender partner number in control record is default

We have created some KU partners in WE20 for sending billing documents to the SD bill-to partner but is running into an output error EA608 (EDI: Sender partner number in control record is default) on the billing document when trying to create IDOC's.
Settings on partner:
Partner: 12345
Partner type: KU
Partner function: BP
Message type: INVOIC
Application: V3 : Billing
Output type: ZEDI : US EDI Invoice
Process code: SD09 : INVOIC: Invoic
EDI Standard         X
Message type         810
Version              004010
Any idea to what the problem is?
BR
Joergen

Hi Joergen,
we also have similar problem to send out ordrsp. Could you tell me how to solve this problem as I saw tht this problem of yours has been answered.
Thanks inadvance for your reply,
Lily

EDI: Sender partner number in control record is default

Hello!
Another problem... in SUS - MM, Plan Driven Procurement
I try to send PO from MM to SUS. But in the messages I get following
error: "EDI: Sender partner number in control record is default"
Message no. EA608
SAP Note Number: 111342 doesn't help
the logical systems are maintained!
Any idea about this problem?
Kind regards,
Barbara

If this is in regards to an ASN: Check to see if this customer buys several divisions or is relevant for one division only. In our instance of SAP, we found that it didn’t go to the Customer Master division setup relevant to the division on the ASN to get the ACCT AT CUST field, it went to the first in the sequence of divisions and got that ACCT AT CUST field information. That information was not filled out as it was a new division and that is what kept the output from happening. For example: we had divison 02, 04, 06 and 08. We added division 03 and extended all customers to division 03. Those customers that only bought division 04 just stopped sending ASNS. The ASN was for division 04, but SAP logic was retrieving the ACCT AT CUST information (SALES tab, not CORRESPONDENCE tab) for divison 03, but we didn’t have that filled out.
Hope that helps.

Statusrecord 37:Sender partner number in control record is default

Hi all
I am sending MATMAS data from one R/3 to another R/3 in ALE.
when i am testing it from we19..... I'm the data is not sent insted it is being saved in database.
In WE05 I can see the following error.... and the lights are green.
statusrecord 37:Sender partner number in control record is default
Please help me
Thankyou
SIMON

Hi Joergen,
we also have similar problem to send out ordrsp. Could you tell me how to solve this problem as I saw tht this problem of yours has been answered.
Thanks inadvance for your reply,
Lily

Receiver partner type in control record is default"

Hi all,
I am Getting 56 Error"Receiver partner type in control record is default".
When I go to that perticular IDoc under control record under parter tab I am providing "PARTNER TYP" AND PORT.When I save these details th idoc is getting posted.
The port ifo is present in we21.I checked RFC Destination,It is fine.
Now where to give this information centrally since I have to manually enter this every time.
Thanks,
SrinivasaP

Hi,
If error is 56.
Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
Please check receiver IDoc Adapter is configured with the said details are not.
And if possible map the values in EDI_DC40 control record.then you need not to give these details every time.
Regards
Chilla..

56 error,EDI: Receiver partner type in control record is default

Hi all,
When I trying to post the IDOC the 56 error is shown.
I checked the partner profiles and found fine.Please clarify.
Thanks,
Srinivasa

Hi,
this means that your IDOC has some errors
you can see it by clicking on the status in We02
then you will know exactly where the error is located
in inbound processing you should see status 53 - successful
BTW
to check IDOC errros with XI:
/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
Regards,
michal

Message control attributes for EDI 846, 947

Hi experts,
I need to configure partner profile for these EDI transactions: EDI 846 and EDI 947. What should be entered in these fields of message control tab:
Application, Process code, Message type? Also what are the IDOC types for these?
Thanks.
Regards,
Abhinav

Go to WE20 and create the partner 1000 type KU and maintain the outbound idoc properties.
Regards
Shravan

Determine Confirmation Control Key for UB STO

Hi,
For NB PO's, the confirmation control key (CCK) can be determined by the vendor.
How can I determine the CCK for a UB STO when I am using a supplying plant instead vendor?
CD

Hi,
Normally the confirmation control key will be defaulted from the config maintained at sprommpurchasing--confirmations for NB or UB.
Regards,

User exit EXIT_SAPLIEDI_011 for determination of PO item for EDI LIV

Hi,
I am trying to get LIV via EDI working. The incoming INVOIC02 IDOCS mark an error when processing: there is no PO item in the ZEILE field of E1EDP02-001. I thought I could use EXIT_SAPLIEDI_011 to get the PO item number determined and to get this problem solved. But I cannot see where the exit is called during the LIV process. Does anyone know where EXIT_SAPLIEDI_011 is called and how I can test this?
Thanks,
Joris

My friend.... to view EXIT_SAPLIEDI_011 you can go to SE37.
You will not find it using where used list as it is done via CALLL CUSTOMER-FUNCTION.
If you think it satisfies what you are looking for, please implement it as a part of a project in CMOD and create the include in the FM to test it.
This will be triggered when a material management is received via EDI.
Naveen Vajja

Creating records for Partner function ?

Dear all,
I am creating partner function as a sales partner, can i maintain record for the same?
Bcoz in condition table there is no field for partner determination.
Can u plz send me some details regarding the same.
Thanks & Regards,
PM

hi,
i have got the procedure for commission agent.. just transform the report to your sales partner requirement instead of comm agent requirement.
hope it helps you.
For creating commission agent, you have to follow below steps.
1) Establish Partner Functions for the Commissionee(s)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA
2) Assign the Partner Functions to Partner Procedures
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA
3) Create a Partner Procedure for the Commissionees
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA
4) Create New Customer Account Group(s) for Commission Agents
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER
Transaction Code: OVT0
5) Assign the Partner Functions to the Customer Account Group(s)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT
Transaction Code: VOPA
6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header
Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions
Transaction Code: VOPA
7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA
8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent)
Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY
Transaction Code: SE11
9) Edit MV45AFZZ userexit_pricing_prepare_tkomk (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38
10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38
11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38
The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).
13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: OV24
14) Create Condition Tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: V/03
15) Create an access sequence containing the new tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: V/07
16) Create a new condition type
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES
Transaction Code: V/06
17) Add the Condition Type to the Pricing Procedure
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES
Transaction Code: V/08
11) Create Commsission Report ZZCOMMISSION (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38
regards,
Siddharth

Error in SWWERRE "No personnel control record exists for accounting area 99"

Dear Experts,
The standard job for restarting of workflows with temporary errors , SWWERRE, has suddenly started failing.
The message obtained in Job Log is "No personnel control record exists for accounting area 99".
The Payroll Control Record for Payroll Area 99 does not exist as it is a non-payroll relevant area.
There has been no change in HCM configuration or Job characteristics.
What could have triggered these sudden failures.
Please suggest.
Regards,
Shilpa A.

Hi Shilpa
This is not an issue with the report RSWWERRE (Job SWWERRE).
It must be trying to pickup work items which are in Error State (temporary) - that item may have this data issue - Run Report RSWWERRE from SE38 and debug, you will come to know.
Check if:
1) The error WI belongs to TRIP (BUS2089)
2) Put a break point in FORM SUB_ABRECHNUNG(SAPLHRTR) and run report RSWWERRE (if the work item is still in TEMPORARY ERROR SATE and has not converted to permanent error) ..... debugging should stop there if the above point is correct
3) This will give you the Trip and Employee number - check if the data is consistent (BAPI_TRIP_CHECK_STATUS)
4) This usually happens when you use &TRIP.AVSEXORADAUTHORITYLEVEL& in the binding (of the error step)
if this is true, correct the data and it should work else delete those work items and restart the job (remember to correct the data to avoid future issues).
If not,
still the fist point holds true, "It must be trying to pickup items which are in Error State - that item may have the issue - Run Report RSWWERRE from SE38 and debug, you will come to know." Some errors are deep rooted and cannot be caught by the job
Also check if note 1452535 is relevant for your release.
Regards,
Modak
Message was edited by: Modak Gupta
............Also check thread: ..
http://scn.sap.com/thread/2021322

Include segment in Control record of idoc type PEXR2002 and PAYEXT

Gurus
This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
Is it possible to add segement in control record for each payment method?.
Thanks for your time and consideration
Auroar

It may depend on how the IDoc is created.
From a file.
Sent via a Remote Call.
You would then need to code it for this Message type only.
I would take a copy of the standard Function and change that. You would have greater control then.
Why is the partner number wrong anyway. Can you not just create another partner profile(s).
Message was edited by:
Martin Shinks

Determination Idoc Control data - Outbound

Hi Guru's
I would like to know how to get the idoc control data, like receiver port and receiver partner. For example:
I have an ABAP program which collects the IDOC data at the end I want to send out the IDOC, but what is the best way to determine the receiver information? Or how does it work in relation with partner profiles?
Best regards,
Guido Koopmann

You don't need to specify all of the information - your distribution model will take care of it. Do something like this snippet of code for the control record for output-based processing:
* Populate the control record
gs_ctrlout = gs_ctrlin.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
    IMPORTING
      own_logical_system             = lv_logsys
    EXCEPTIONS
      own_logical_system_not_defined = 1
      OTHERS                         = 2.
IF sy-subrc EQ 0.
    gs_ctrlout-sndprt = 'LS'.
    gs_ctrlout-sndprn = lv_logsys.
ELSE.
ENDIF.
gs_ctrlout-serial(8)   = sy-datum.
gs_ctrlout-serial+8(6) = sy-uzeit.
If you have a standalone program, before calling MASTER_IDOC_DISTRIBUTE, you just need to fill the message type and IDOC type in the control record.

Problem in modifying control record

Hi All,
My scenario is Purchase order to Sales order. Once PO is created IDOC will be created and that idoc will be taken as source and i will be modifying the idoc in abap mapping as per requirement.
All the segements are being modified and getting updated in IDOC but when i am trying to change the control record its not getting reflected in the r/3 but when i check in moni before comming to r/3 the xml struture has changed as per my requirement even for control record also but while comming from XI control record is not getting changed.
I would like to change senderpartner and sender partner type in control records.
every configurattion steps has been done correctly.
Would request your experiences if you would have faced any this type of situation in your projects.
Thanks in Advance.

Apply Control Record Values from Payload
If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values.
http://help.sap.com/saphelp_nw04s/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm

Partner determination in control record for EDI

Similar Messages

Maybe you are looking for