Problem in Idoc type

Hi Experts,
I am facing one strange issue in idocs.
I am having a scenario where for particular LS i have assigned HRMD_A06 basic type and ZHRMD_A06 extension in partner profile.
and i am trying to implement badi HRALE00OUTBOUND_IDOC.
in this badi at runtime wrong message type is getting picked up at the runtime(checked in debugging). But at the end it displays proper basic type.
so for me it is getting difficult to write logic in this badi.
Please guide is there any particular setting apart from partner profile where we assign message type to LS.

Hi,
In problem in idoc type , that below link will helpful to you.
Try this link,
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
Regards,
Sekhar

Similar Messages

Mapping problem for IDOC Type DESADV

Dear all
I need to change Segment E1EDP07 in the message type DESADV.
I should concatenate VBELN and VGPOS into BSTNK.
I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.
So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.
Do you have any ideas how I can do this?
Herbert

>
Herbert Schlup wrote:
> I have 2 entries for my DWSADV01
>
> 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1
With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine DESADV_IDOC_PARSE in the function.
But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV is used with process code DESA and message type DESADV with IDoc type DESADV01. So you might be using IDOC_INPUT_DESADV function and unfortunately there are no user exits to handle your requirement.
My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly
KR,
Advait

Incorrect IDoc type ZSBC052 in the ALE definition of the source system

hi guyz,
i am getting the following error while checking the source system in bi.
Incorrect IDoc type ZSBC052 in the ALE definition of the source system RSAR 373
please guide through your expertise.
regards,
raps.

Hi,
Check the below given thread,
[Source System Check Problem;
[Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR;
Regards,
Durgesh.

Message type idoc type problems

Hi,
I'm facing a problem in idocs. I'm sending idocs with message type ORDRSP and idoc type ORDERS05, but for some reason in SAP, the idoc is always picking up a different message type ORDERS and the partner profile part is failing because my partner profile is set up for ORDRSP message type. Is there any setting or transaction that sets a default message type for an idoc type in SAP.
Regards,
Vijay

Hi vihay,
yes for the message type ordrsp the basic type is orders05.
u r telling ur geeting problem in inbound idoc?
if that is the case then u have to use in we20 inbound parameters and give the processcode(ORDE) there instead of basictype .CHECK the same and get back to me if any quries
Regards,
Nagaraj

ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot set up identical definitions.
I suppose I should 'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
Thank you in advance!

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

Problems with PORDCR101/2 IDOC Type

Hi All,
I am new to SDN so not sure of the protocol so please bear with me.
I am trying to use IDOC type PORDCR101 to create purchase orders.
In the segment E1BPMEPOHEADER I have mapped the the DOC_TYPE to NB (with the corresponding E1BPMEPOHEADERX set to X)
But I am still getting a strange error message
Document type ZU not allowed with doc. category F (Please check input)
ZU is a bespoke requestion that exists in the system, but nowhere is this mapped. The standard NB Purchase order type exists in the system.
If anybody can shed some light, I can provide the complete mapping if this is useful.
thanks
Shashi

Hi G.Ganesh Kumar,
The partner profile in WE20 the Partner Type is set correctly, the inbound parameters have message type PORDCR1 set correctly with the BAPI process code.
I have no problem generating the idoc, I get the error 51 with the above description when the idoc tries to post.
Shashi

Problem LSMW + IDOC method for message type : MATMAS

hi friends,
I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
data : material, industry type, material type, description, Basic unit of mesure.
Please help me.
Balaji.T.

Hi,
I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
Regards,
Klaus

IDX2 Communication Error - Problem with only 1 IDoc Type

Trying to import metadata via IDX2. All IDoc types have imported succesfully, except DELVRY03.
I get a message saying "Communication Error" Message #: IDOC_METADATA407.
I have tried DELVRY01 and it imports fine. But, DELVRY02 and DELVRY03 both give the "Communication Error" messages.
Any ideas why this one particular type will not import? Settings/logon have not changed.
Thanks

FYI, Update... I think I may be on to something here...
All checks in WE30 return okay.
I debugged the IDX2 program, error is occuring in the 'IDOCTYPE_READ_COMPLETE' function call. It is returning with message: 'Structure of segment E1EDD10 is unknown'. Did search on this in OSS and found note #491264 -- Output of IDoc DELVRY02/DELVRY03 does not work
Symptom
You want to display IDoc DELVRYnn (nn = 02,03), SHPMNTnn (nn = 03,04,05), or PLNSHPnn (nn = 01) via the IDoc documentation transactions. The sys
Comment: This relates only to the display of the IDOC structure. The IDocs work for the data exchange.
Still working through the note to see if this will fix the issue, but I just tried to import in SHPMNT03 and I get the same error.
Thanks.

Problem with IDoc for an outbound delivery

Dear All,
I am facing a problem with the IDoc defined for an outbound delivery.
Scenario:
Implementation of a small enhancement for an IDoc (DESADV, DELVRY01) created for an outbound delivery (in VL02N).
What I did:
I implemented the EXIT_SAPLV56K_002 exit in the V56K0001 enhancement, activated in SMOD, assigned V56K0001 component in CMOD and acivated it. Then I put a breakpoint on the ZXTRKU02 include. For me everything in SMOD and CMOD looks OK.
I have also created a partner profile, port, outbound message config. (message DESADV, basic type DELVRY01, application V2, output message type LAVA, process code DELV. function module used for this process code is IDOC_OUTPUT_DELVRY).
What I can do:
I can issue an IDoc message, it looks ok and contains the standard data.
Problem:
It seems that the enhancement does not work. Finally I put there only one line of code to avoid a program bug and just to check . The system does not stop at the breakpoint (set on the ZXTRKU02 include in the EXIT_SAPLV56K_002 exit).
Am I using the proper exit? I appreciate any suggestions.
Thanks,
Grzegorz Skorus

Hello Grzegorz
Not an expert on this, but noone is responding so I thought let me try and help you. You seem to be doing the right things as mentioned in OSS note 1498409.
Firstly since this can be called form Shipment Idoc also, you may need to make a differentiation by the interface parameter 'MESSAGE_TYPE' or segment name. See the attached OSS note, though it belongs to older releases, it may help you.
Also help says 'The callup of this function module is programmed for each enhancement of the internal table for the IDoc (in other words, when you add an extra segment'. So may be you need to add an extra segment/field to make it work.
Futher the user exits are replaced by BADIs. May be you should use exit_badi_v56k.
Hope this helps and others will pitch in.
1498409 - Valuation Type unavailable when creating deliveries using IDOC
631913 - Exit after formatting delivery IDoc type DELVRY

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

Modify BP in CRM using Idoc type BUPA_INBOUND_MAIN_SAVE_M03

Hi,
I want to modify(add) a new role to an existing BP in CRM.
I am using the Idoc type BUPA_INBOUND_MAIN_SAVE_M03 for the same.
The problem that I am facing is that even though I am wanting to modify the BP, whenever this IDoc is posted the existing roles (seen in table BUT100) for the BP get deleted and the new role is added through the interface.
Please can anyone assist me as what is going missing in the filling the segments.
Regards,
Taher
the segment structure is as below.
BUPA_INBOUND_MAIN_SAVE_M03
E101BUS_EI_EXTERN
E101BUS_EI_HEADER
        E101BUS_EI_INSTANCE
    E101BUS_EI_CENTRAL_DATA
        E101BUS_EI_ROLES
            E101BUS_EI_BUPA_ROLES
                E101BUS_EI_ROLE_DATA
                E101BUS_EI_ROLE_DATA_X

Hi,
I figured out the solution to this.
Get the existing roles for the BP using the FM BAPI_BUPA_ROLES_GET.
Append the existing roles along with the new role that is required to be added.
the task type should be I (Insert).
When the Idoc is posted the existing roles do not get overwritten and the new role is added.
Regards,
taher

Problem in Idoc creation in ME22N

Hi All,
We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
Are any other config settings required to be maintained for this?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj

Performance problem in IDoc receive (DELFOR01)

Hi,
I have serious problems in receive of Idoc Delfor01 (IDOC_INPUT_DELINS). We receive more than 3000 Idoc daily of this type and the process of then during all day....
One of more common error is foreing_lock of VBAK table. This error occurs in the Form beleg_sperren (line 459 from IDOC_INPUT_DELINS) when the process try enqueue one vbeln entrie from VBAK (o think by the high number of Idoc received) and, the process waits a large time trying enqueue the table entry until the error...
When I analyze the IDOC_INPUT_DELINS i see a batch-input for the VA32 transaction (at line 528). I think if call a Bapi instead a Call Transaction have more performance... it´s right?
I would appreciate help with possible solutions to this problem.. Have a better mode to process large amount of these IDoc type? Or have other FM than IDOC_INPUT_DELINS with better performance???
Regards,

Not need immediatly, but a quickly possible... In WE20 if I choose the background program the process will executed* fastly than I choose Imediattly start?
*executed via schedule job of program RBDAPP01.
I stil reading the notes above..

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Problem in Idoc type

Similar Messages

Maybe you are looking for