For Assistance: IDocs in Status 02

Dear SAP Peeps,
We have some issues on an existing HR interface. Approximately 2 to 3 idocs per two weeks use to end after their generation in PGH. They end up in status 02-Error passing data to port. Error description is "codepage of receiver system can't determind. receiver destination was: BB1CLNT100".
I've checked the RFC destination, port settings, and connectivity and they seems to be ok.
Can you help me on how to solve this issue?
Thanks!

Worth to have a look at this thread
Error handling problem with outbound idoc status 02 and XML HTTP Port
Regards
Vivek
Reward points for all the useful answers

Similar Messages

Performance issues in using RBDAPP01 for reprocessing iDocs with Status 64

Hi All,
I am using the Standard ABAP Program 'RBDAPP01' for reprocessing Inbound iDocs with Status 64 (Ready to be posted).
When this is scheduled as a job in background, I find that it opens multiple sessions and occupies all available dialog sessions.
This in turn slows down the entire system.
Also, I find the addition 'Packet Size' on the selection screen for the program.
Is it related in any way to the number of sessions the program creates?
Any pointers in resolving this issue will be extremely helpful.
Thanks in advance.
Regards,
Keerthi

Hi,
When you mention Parallel Processing, it becomes active only if I choose that particular option on the selection screen right?
In my case, I haven't chosen parallel processing, but still the overall system performance seems to have fallen very badly.
Now please correct me if my understanding is wrong.
If I increase my Packet Size, it should improve the system performance, but will increase my runtime for the selected iDocs.
But as I have not selected parallel processing in this current situatuon, it should not have any impact here.
Have I summarized it rightly?
Thanks in advance.
Regards,
Keerthi

Outbound IDOC in status 12

Hi all,
We have posted outbound IDOC from SAP R3 system to the middleware. Middleware system has received all the IDOC except few(2) idocs and in the very next day again they confirmed that they have not received 3 idocs.
missing idocs were manually processed to have a immediate solution.
we would like to konw how to trouble shoot this scenario?
Following checks were done from our side.
1.There are no entries listed in SM58(tRFC queue)
2.No corresponding entries in the table ARFCRSTATE
3.No network issues.
4.No clue in the Gateway trace.
Is there a way to trace the IDOC stats??
Clara

Hi,
Status 12 means that the IDoc has been passed over to the receiving system.
The report RBDMOIND checks that the transaction ID for all IDocs in status 03 are not stuck in the RFC layer If no entry is found, the status is changed to 12.
The receiving system has not acknowledged that this specific IDoc has been received, it is only an indicator that the RFC call is not pending.
aRs

Reprocessing IDOCS with status 52

Hi all,
I facing a problem with IDOC status 52.
After correcting the error it had given, I want to reprocess it again.
Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
Regards,
Rahul

Hi Rahul,
You can use the below Programs for IDocs Reprocessing:
RBDMANI2 : Reprocess Idocs manually
RBDMANIN : Posting of IDocs with Status 51
RBDMOIND : Outbound Idocs status 03->12
RSEOUT00 : For Processing 30 Status IDocs
RBDAPP01 : For Processing 64 Status IDocs
RBDAGAIN : Reprocess Incorrect Outbound IDocs
RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
Regards
Aneesh.

Inbound IDoc used for updating Sales order status

I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
1. What are the difference between all the ORDERSxx Idoc types?
2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
Thank you. Points will be awarded appropriately for helpful comments.

Hi,
1.Intially standard IDOC types "ORDERS01" is having limited
      segments. After few months the requirement got increased to
      add more fields to "ORDERS01".So,once you release the IDOC
      type you can not add any more fields .So SAP come up
      with "ORDERS02" with new fields.Like that all IDocs types have
      some more new seg ments.
2.You can use ORDER05
3. Yes you can use same IDOC type

Query on IDOC Ack (STATUS) config in XI for a specific partner comm.

Hi Experts,
Is it possible to configure the IDOC Ack (STATUS.SYSTAT01 message) in XI for a specific partner communication? We want to configure our system like ALEAUD but the message type should be STATUS.SYSTAT01 and the acknowledgment should be send to sender system for a specific partner only if XI receives any IDOC like (Orders) from that specific partner. For other partners (same sender system) we donu2019t want this acknowledgment settings and configuration. If possible please provide the configuration filters steps etc. Thanks for your valuable inputs in advance.
Thanks,
Satish
Edited by: Satish Jaiswal on Jan 8, 2009 2:55 AM

Hi Husain,
I have the document you have mentioned. Please note my requirement is to filter the Ack while creating and sending to R/3 based on Partner and Message type. The document provides info only on Message type filter but not parner specific for same sender system!!! Any help appreciated. Also note: BPM and Alert is out of scope.
Looking for some ALE configuration tricks to achieve this.
Thanks
satish
Edited by: Satish Jaiswal on Jan 9, 2009 2:40 AM

Splitter program for processing the IDOCS with status 64.

Hello folks,
I have a requirement explained below. I am looking for a sample code which could help me to jump start with initial development.
Requirement:
Develop a splitter program which retrieves all the IDCOS with status 64, create and schedule batch jobs with 200 IDOCS each. The splitter program with be scheduled every 15 min.
Restrictions
Only 150 batch jobs can be created at a time.
Estimation
There may be around 36000 IDOCS with status 64 every hour.

Srinivas,
Here is the explaination why we require a splitter program.
Using RBDAPP01 parellel processing
Let us assume there are 4 servers A, B, C and D in a server group. If we select RBDAPP01 parellel processing there will be too many RFC calls to the servergroup.
(there are some more RFC calls later on for Order creation for example). As there is a restriction with number of RFC calls, we need to clear other RFC's before making new one. This is making complex and messy.
Using RDBAPP01 serial processing
For the volume of orders getting created each day, it takes a week to process those Idoca created in one day. Hence it is not a good solution.
Splitter program
We spawn 150 batch jobs with 200 records each. This way if we think it takes 20 min for each job to complete...by the end of 20th min we must had processed 30000 idocs.
Hence it is the solution offered.
Srinivas...still this confuses me..but if I am wrong anywhere please correct me.
But your initial response has helped me a lot. Everything was blank to me, ur reply made it clear over the requirement.
Thanks a lot,
Naren

Exit for CJ20N where system status changes can be captured

Hi Experts,
I need exit for CJ20N where system status changes can be captured
for both the below cases
1) When WBS Element is having Networks inside it
2) when WBS Element is having no networks inside it
EXIT_SAPLCOBT_001 --->>> ZXCO1U01 , will work for 1) , but not for 2)
i want an exit where status change gets captured for both cases 1 and 2 and
will do further processing according to client needs based on status change
Need to trigger IDOC on status change of WBS element.
If WBS is having network inside it , then network status changes also with WBS status change
and IDOC should trigger for WBS also.
I just want suitable exit / place for coding . Rest i can do.
if no suitable exit / BADI , then what is the best possible place where i can go for Implicit Enhancement
Best Regards,
Gaurav
Edited by: TheGaurav on Oct 25, 2011 7:08 AM
Edited by: TheGaurav on Oct 25, 2011 7:12 AM

I am kind of stuck in a similar issue. I need to perform custom validations on standard fields which cannot be done through OPSI or OPUC transactions. 0007 or 0002 User exits seem to assist on custom field creations/validations. However, I do see people posting the following BADIs which may be useful.
CO_SRULE_CHECK
PROJECTDEF_UPDATE
WORKBREAKDOWN_UPDATE (which you already tried)
WBS_FIELDS_FOR_ASSET
CO_SRULE_CDOC
Let me know if any of these worked out...
AN

IP Job in BW finished, but how can I check the IDoc receive status in BW ?

Hi,experts
After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
and how can I do now ? or how can I check the IDoc receive status in BW side?

Hi,
I too had the same problem, i executed the following to solve the proble, may be this will help you:
1) Go to T-code SM58 and select TRFC and press F6,
2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
Thanks,

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Best practice for migrating IDOCs?

Subject: Best practice for migrating IDOC's?
Hi,
I need to migrate some IDOC's to another system for 'historical reference'.
However, I don't want to move them using the regular setup as I don't want the inbound processing to be triggered.
The data that was created in the original system by the processed IDOC's will be migrated to the new system using migration workbench. I only need to migrate the IDOC's as-is due to legal requirements.
What is the best way to do this? I can see three solutions:
A) Download IDOC table contents to a local file and upload them in the new system. Quick and dirty approach, but it might also be a bit risky.
B) Use LSMW. However, I'm not sure whether this is feasible for IDOC's.
C) Using ALE and setting up a custom partner profile where inbound processing only writes the IDOC's to the database. Send the IDOC's from legacy to the new system. Using standard functionality in this way seems to me to be the best solution, but I need to make sure that the IDOC's once migration will get the same status as they had in the old system.
Any help/input will be appreciated
Regards
Karl Johan
PS. For anyone interested in the business case: Within EU the utility market was deregulated a few years ago, so that any customer can buy electricity from any supplier. When a customer switches supplier this is handled via EDI, in SAP using ALE and IDOC's. I'm working on a merger between two utility companies and for legal reasons we need to move the IDOC's. Any other data is migrated using migration workbench for IS-U.

Hi Daniele
I am not entirely sure, what you are asking, Please could you provide additional information.
Are you looking for best practice recommendations for Governance, for example: Change transports between DEV, QA and PRD in BPC 7.0?
What is the best method? Server Manager backup and restore, etc ?
And
Best Practice recommendations on how to upgrade to a different version of BPC, for example: Upgrading from BPC 7.0 to 7.5 or 10.0 ?
Kind Regards
Daniel

How to get Get IDOC Number for Inbound IDOCS

Hi,
I am using the FM -- IDOC_INPUT_HRMD for creating Inbound IDOCS.
I populate the values for Control Record and Data Record and the IDOC is posted successfully and i get the status 53 in the status Table.
But the problem is the field for IDOC number(DOCNUM in IDOC_STATUS Table of the FM ) is empty.
How can i get the DOCNUM for the IDOC posted as a result of this FM ?
regards,
Siddhartha

Hi Siddhartha,
I think you cannot call IDOC_INPUT_HRMD fm directly from the external program as this fm only handles the application logic part and not the idoc number generation and save part.
So I think you have to call IDOC_INBOUND_SINGLE from your external program and then get the IDOC number.
Then if you need the status records then you need to call another fm and feed IDOC number that you have got from IDOC_INBOUND_SINGLE (there is one IDOC_READ_COMPLETELY but it is not a remote enabled fm)
<b>OK, I just found one RFC enabled fm which you can use,
<b>EDI_DOCUMENT_READ_ALL_STATUS</b></b>
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

InfoPackage loading giving IDOC Error: Status 51

Hello Experts,
1) I created a DB view (ZZVIEW05) in the SD area on R3
   and it extracts data OK in RSA3.
2) I replicated the DataSource in BW, Created InfoSOurce
   activated and created an InfoPackage.
3) Scheduling the InfoPackage is failing with an Error:
      Transfer(IDocs and TRFC):Errors Occurred
         Request IDOc: APplication document not posted
For the Error, I right Clicked and looked at the IDoc status in the Source System (R3 where we are getting the data from).
The Idoc with Error has a status of 51 and has the following message:
Any suggestions ?
Thanks, BB
Function module not allowed: ABI_IDOC_DISPATCH
Message no. B1252
Diagnosis
     The function module ABI_IDOC_DISPATCH and the
     application object type which were determined
     are not valid for this IDoc.
Procedure
     1. Please check that the process code in the
         inbound partner profile is correct.
     2. If this is the case, you should check the ALE
         inbound methods ALE inbound methods for the
         process code and see whether the specified
         function module and application object type are
         correct.
     3. If this is also the case, then the function
         module and the application object type are not
         permitted for the logical message type, message
         variant, message function and basis type that
         are contained in the IDoc control record. You
         should check whether the correct values have
         been assigned to these fields in the control
         record. If they do have the correct values,
         then the assignment to the function module and
         the application object type needs to be
         maintained.

Hi Dinesh & Sat,
I tried following:
Using WE19.....I was able to manually pump the IDOC that got stuck in ALE inbox on R3 side...then R3 was able service the request and send data to BW.
It seems the correct function module (R3 side) to process an incoming BW data request is RSAP_IDOC_DISPATCHER.
Instead ABI_IDOC_DISPATCHER is being invoked, by default, which is giving the problem (seems to be some kind of authorization issue!).
In WE20, I changed the partner profile to process using RSAP_IDOC_DISPATCHER. BUT somehow it is not being invoked.
I suppose some other setup (table entry) is conflicting with my setup ....
Any clues ?
Thanks, BB

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Function module for posting idoc

Hi,
For Inbound Idoc
In function module for posting the Idoc what should be given as the return_variable.

Hi,
it depends on application.i have written some piece of code for my requiremnt.chek it,may be it will help u.
FORM idoc_status_ord_change
     TABLES idoc_data    STRUCTURE edidd
            idoc_status STRUCTURE bdidocstat
            r_variables STRUCTURE bdwfretvar
      USING idoc_contrl LIKE edidc
            value(retn_info) LIKE   bapiret2
            status       LIKE bdidocstat-status
            wf_result    LIKE bdwf_param-result.
CLEAR idoc_status.
idoc_status-docnum   = idoc_contrl-docnum.
idoc_status-msgty    = retn_info-type.
idoc_status-msgid    = retn_info-id.
idoc_status-msgno    = retn_info-number.
idoc_status-appl_log = retn_info-log_no.
idoc_status-msgv1    = retn_info-message_v1.
idoc_status-msgv2    = retn_info-message_v2.
idoc_status-msgv3    = retn_info-message_v3.
idoc_status-msgv4    = retn_info-message_v4.
idoc_status-repid    = sy-repid.
idoc_status-status   = status.
APPEND idoc_status.
IF idoc_status-status = '51'.
    wf_result = '99999'.
    r_variables-wf_param   = 'Error_IDOCs'.
    r_variables-doc_number = idoc_contrl-docnum.
    READ TABLE r_variables FROM r_variables.
    IF sy-subrc <> 0.
      APPEND r_variables.
    ENDIF.
ELSEIF idoc_status-status = '53'.
    CLEAR wf_result.
    r_variables-wf_param = 'Processed_IDOCs'.
    r_variables-doc_number = idoc_contrl-docnum.
    READ TABLE r_variables FROM r_variables.
    IF sy-subrc <> 0.
      APPEND r_variables.
    ENDIF.
ENDIF.
regards,
nagaraj

For Assistance: IDocs in Status 02

Similar Messages

Maybe you are looking for