Application document created by IDoc

Guys,
Is there a function module that would give me the Application document that got created by posting a given IDoc? In other words, if I know the Idoc number, is there an easy way to get the application document number, once the Idoc posted succesfully?
All this from an ABAP program is what I mean.
Your help is appreciated.
Thanks a lot,
Viktor

these are some of the functions which you can use for the application document
EXPORTING
             VALUE(MASTER_IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
             VALUE(OBJ_TYPE) LIKE SERIAL-OBJ_TYPE DEFAULT ''
             VALUE(CHNUM) LIKE SERIAL-CHNUM DEFAULT ''
       TABLES
              COMMUNICATION_IDOC_CONTROL STRUCTURE EDIDC
                    MASTER_IDOC_DATA STRUCTURE EDIDD
             EXCEPTIONS
              ERROR_IN_IDOC_CONTROL
                    ERROR_WRITING_IDOC_STATUS
                    ERROR_IN_IDOC_DATA
                    SENDING_LOGICAL_SYSTEM_UNKNOWN
Hope this might help you

Similar Messages

BI extraction error -- Application document not posted - IDOC Status 51

Hi,
I am getting the following error while extracting data from ECC to BI.
'Application Document not posted'
I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
I have already checked partner profile parameters with Basis and they claim everything is okay.
Do you have any ideas what might be the issue?
Thanks,

Hello Rajendra,
You can review the note 417307 which contain information about the MAXSIZE of a package size. This is a collective note which contain more notes to other extractors.
417307 - Extractor package size: Collective note for applications
549184 - FAQ: What is important for extraction
157652 - Main memory requirement for extraction from R/3
You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
You can also review the correction note 1147326.
Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
I hope that the information can help you.
Regards,
Daniel

Return order with reference to the billing document created via IDOC.

Dear Colleagues,
I’m struggling to understand and confirm whether standard functionality of ORDERS05 idoc allows creating a return order with reference to existing billing document?
I have tried using standard segment E1EDK02 and E1EDP02 with qualifiers 009,010,011,087 but unfortunately idol is not creating a return order with reference and ignoring this segment.
Have any one came across similar problem? If yes then will be grateful for sharing his experience.
Best regards,
AL

Dear Friend
Welcome to SDN
Return order is itself a challenge to SAP standard settings
There are some scenarios
1. Return order qty should not be increasesd say Billed qty of material X is 20 units
While returning Material X should be a maximum of 20 units
If made 21 it should throw error T code OVAH message class V4 message no 299 convert from warning to error thro customization
2.Return order should be created only once referencing billing doc
To control that T code SE91 message class V1 message no 499 convert from warning to error thro ABAP help
3 Your issue is same like case 1 but the material X is entered as second line item in the return order with some qty
This case system is not throwing even a warning
Yes correct
This is to be handled with userexit
Discuss the same with ABAPer
Check these threads on return issues which is of different scenario than of yours
Forum post in ERP - Sales and Distribution (SD) General: Order Qty.
Order Qty.
Forum post in ERP - Sales and Distribution (SD) General: Return order
Return order
Regards
Raja

IDOC is created with status 51( application document not posted)

Hi experts
iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
but the IDOC is created with status 51( application document not posted)
the details error shows:
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
previously i used same test data that time it was working fine,
please tell me how can i fix the issue.
regards
vasavi

Key in your Idoc number in BD87, execute
select the error message and then follow the menu path :
EDIT --> restrict and process (Select)
In the next screen UNCHECK the Bkgd Processing and execute
Now EDIT --> Process --> foreground from error or in foreground mode.
This will lead you the screen where it errored out.
Thx
PSR

IDOC Number for a Application document

Hi frinds,
Using Idocs we create application documents like Sales orders(inbound),invoices, delivery etc (outbound) to create application document in some other system or used in case of B2B scenario.
my requirement is can we get the Idoc # form the slaesorders number using some function module (to get the idoc #'s of huge number of sales orders). however we can find the sales order number form the Idoc number using WE05 i want the reverse way.
Thanks,
vin.

Hi,
If your requirement is like Xi generates an outbound idoc to R/3 which is different to inbound idoc number of R/3.
USe SREL_GET_NEXT_NEIGHBORS ,
object-objkey = idoc num object-objtyp = 'IDOC', max_hops = '99'.
You can get the list of outbound,inbound idoc numbers and sales order .
Thanks and Regards,
P.Bharadwaj
Edited by: Bharadwaj p on Jun 14, 2010 8:31 AM

Inbound idoc application document not posted

Hi,
idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
This field is not being provided with any value but still the idoc is getting error with this field.
"Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the idoc is getting error message as 51 (with the same field).
Please provide your valuable suggestions to solve this problem.
I had created one cm and tried but still the same message is comming.
Awaiting your help.
thanks
rohith

Thanks for all your suggestions..
The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
So, this function module cannot be modified which is not my requirement.
My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
Hope you have got a clear requirement.
Waiting for your response.
Thanks
rohith

Inboun IDOC status 52--Application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

I am attaching how we documented the process in our troubleshooting guide. Graphics were not pasted.
21.3       Manually run IDOCs reported as 52.
It is possible that IDOCs are found in status 52 for the daily updates.   In principle IDOCs 52 can not be re-proceeed, but there is a way to push the appropriate data from a source system, e.g. ERP.    Following is the process.
21.3.1     You find IDOCs in status 52 in WE02.
21.3.1     Open table EDIDS.
Perform 2 searches for parameter STAPA2 and STAPA1 in status 52 and download the entries for each column to an MS Excel file.
21.3.2     Adjust the MS Excel file.
The strings STAPA2 and STAPA1 have to be truncated and separated into 3 different fields for processing: First 2 characters are the Plan Number, next 2 the Object Type, and next 8 the Object Number.
21.3.3     Manually process the entries via transaction PFAL from the source system, e.g. ERP.
The entries must be processed in the following order sorting by Object Name:
u2022     STAPA2s first, then STAPA1s.
u2022     Each organized by O, S, P, C, and CP.
21.3.3.1     Running individually for each entry.
By running PFAL with the individual entries: Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOC will be passed to target system for processing.
21.3.3.2     If there are many entries for processing.
If there are many STAPA2 and STAPA1 for processing.
u2022     Create a text file like the one below with the entries as mentioned above.
u2022     Logon into the source system and make sure CATTs are allowed..
u2022     Via SCAT, create a CATT that emulates the execution of PFAL entering Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOCs will be passed to the target system for processing.
. Create the text file with the entries.
. Execute the CATT ... the respective IDOCs will be passed to target system for processing.

IDoc: Status: Application document not posted

Hi Friends,
       I am New to ALE/IDOC. Based on the ALE_QUICKSTART documentation. I have tried to send material from one client to other client. (within system) To do that
I have created two logical systems and assigned them to corresponding clients.
Created a RFC destination and assigned logical systems.
Created Distribution model in sending client.
Created partner profile in both clients.
Created Material and send to receiving system using BD10 tcode.
I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and status 01- Idoc generated.
But in receving system (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
I also checked partner profiles in both systmes- both r same.
Kindly tell me what went wrong and what should i do.
Pl.provide answers pertain to this problem only.
Thanks in advance,
S.Senthil

Hi Chris,
        Thanks for ur reply. I am not using is-retail and I have Generated MATMAS idoc in sending system.
      Kindly provide me answer.
Thanks in advance,
s.senthil kumar

Test IDoc data posted into application document correctly

Hi,
I'm new to IDocs.
I need to test some inbound idocs if the data is correctly posted as Application document(PO).
But currently the partner profile is not set in the system.
When i tried to process the idoc using RBDAPP01 i'm getting the status as 'Error passing IDoc to Application'
Is it possible to process idoc by any other way for testing, to create PO and data is populated correclty in PO.
Thanks in advance,
poornima.

Hello,
You can go to the Transaction WE19 (Test Tool for IDoc) and select an Idoc based on the Idoc Type that you want to Test & Post. While Posting the IDoc from WE19, the Partner Profile Check will be ignored and it will not be a Fatal Error even if you've not maintained the Partner Profile for the Incoming IDoc.
Refer to the Following Link which contains Instructions about Testing an Inbound Interface using the Test Tool.
http://help.sap.com/saphelp_nw70/helpdata/en/dc/6b814443d711d1893e0000e8323c4f/frameset.htm
Hope it would be helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

How to trace an Inbound R3 IDoc by seeing application document

Hi all,
How to trace an Inbound IDoc number by seeing application document in R3.
sometimes 'Services from object' also we could'nt able to trace out the IDoc.
'Services from object' option sometimes appears in blank status with no IDoc.
Any possible tracing options?

HI Chitra,
You can findout the Idoc number in R/3 System by using the tr.code WE05 or WE02.
Go throgh the following blog for message monitoring.
/people/alessandro.guarneri/blog/2006/02/14/super-message-monitor-for-sap-xi
Regards
Goli Sridhar

Application document not psted status 51 in ALE/IDOC

Hi Gurus/Experts;
Status number : 51 Application document not psted.
I have configured ALE for distributing material master data. On the outbound side the status of every Idoc is sucess. But on the inbound side some of them are red stating error.
Outbound Side :
we05 t-code.
03 success.
Inbound Side:
we02 t-code.
51 Error.
when I execute the we02 t-code and
Expand Status Record 51
am getting error like : Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT
Please Give me some suggestion on this..
Thanks;
Ravi.

HI jayanth;
thanks for your replay.
we are almost 1 step ahead i think ...
plz suggest me the same...
those steps are very usefull and its cleard the step status type 51 error
now am getting error on inbound side when we execute we02 t-code.
status Error number 29.
Could not determine recipients for message type MATFET
Message no. B1003
Diagnosis
An IDoc of message type MATFET was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks;
Ravi.

RMS stopped. Users told "only documents created in a signed application can be opened in a signed application"

Hi
I hope you can help and that this is the right forum.
We have a RMS 1.0 sp1 server which has stopped working.
Users get "only documents created in a signed application can be opened in a signed application" when trying to protect a document in word or Outlook, and are unable to open previously protected documents.
C:\Users\username\Local Settings\Application Data\Microsoft\DRM - only has the one file in it which is DRM-Machine. the .eul .CLC and .Gic files are missing from this folder.
The server running the rms has an event id 82. " the callers machine certificate has a certificate chain that is not valid"
I ran an irmcheck on the local machine which showed " No user Certificate"
I can connect to the rms server urls , both licensing and certificate with no errors and IE shows the zone to be local intranet.
Can anyone see what my problem might be and suggest why the workstations are not getting their certs and allowed protection? What else should I be checking?
Best Regards
Steen

Hi
Here is the answer which resolved my situation, I hope it helps yours.
Guybrush-Threepwood I've marked your post as helpful as we had installed SP2 but it was not installed correctly and installing correctly was part of the solution.
PROBLEM:
Client began seeing the error:
“Only documents created in a signed application can be opened in a signed application”
On the server we were getting events:
“The callers machine certificate has a certificate chain that is not valid”
CAUSE:
Servers running RMS before SP2 can no longer get a valid Server Licensor Certificate.
RESOLUTION:
1. Install RMS v1 SP2 from:
http://www.microsoft.com/en-us/download/details.aspx?id=14329
2. Locate and then click the following key in the registry.
For the enrollment URL on x86 versions of Windows Server 2003:
HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\1.0\
For the enrollment URL on x64 versions of Windows Server 2003:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\DRMS\1.0\
3. On the Edit menu, point to New, and then click String value.
4. Type EnrollmentURL, and then press Enter.
5. On the Edit menu, click Modify.
6. Type
https://activation.drm.microsoft.com/enrollment/enrollservice.asmx, and then click OK.
7. On the Edit menu, point to New, and then click String value.
8. Type CloudGicURL, and then press Enter.
9. On the Edit menu, click Modify.
10. Type
https://certification.drm.microsoft.com/certification/certification.asmx, and then click OK.
11. Go into the RMS Web interface and renew the SLC
HTH

IDOC-Segment Created a idoc document against Billing document

Dear All,
Thanks in advance.
Already created a idoc document against Billing document and one of the IDOC segment is not in the IDOC document output segments(WE05) actually it missed the segment.
so i want to add the segment which it was missed during generation of IDOC document against billing document.
Example:
a) IDOC document misses one segment let suppose "Seg1".
b) In "Seg1" it have only one field let suppose "Field1".
c) But "Field1" does not have any value while generation of IDOC document so it doesn't create the respective segment in IDOC document.
d) so here, i want to edit the IDOC document to add the "Seg1" in the IDOC document and reprocessing the IDOC document.
Please help on this issue.
Regards,
Sridhar.

Hello,
          If your requirement is to have the Segment even with only 1 Field, you'll have to create an Idoc Extension in WE30.
         In order to populate the Custom Segment, Use the Customer Function '002' in the IDOC_OUTPUT_INVOIC which is EXIT_SAPLVEDF_002 where you can actually insert the Segment as a Child Segment of an Appropriate Segment.
        You can go for Custom segment with the IDoc Extension so that you dont have to manually insert the Segment again and again while reprocessing it.
Thanks and Regards,
Venkat Phani Prasad Konduri

Urgent: Error in idoc(Application document not posted)

Hi experts,
i am getting the error in R/3 side when i am extracting data from it.
i checked with WE07 it's shows the error as follows
"Application document not posted".
it's been urgent how to resolve this issue. please through a light on it.
Regards
Harikrishna N

Hi Hari,
You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
This could be the reason for ur error..
IDoc could not be generated under MC
EDIN: Evaluates the partner data from the MC record
TS70008037
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
this link givs u the req info
[http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
Hope it helps U
Regards,
NR

IDoc Error IDocs showing the status 53 "Application Document Posted".

Hi All
IDocs showing the status 53 "Application Document Posted". But values are not updated in SAP.
Plaese sugggest on this,
Thanks
Ajit K Barik

Ajit, there might have been a dump--check in ST22 or a update termination error, check in SM13.
Either of these you'll have to take help of your ABAP consultant to analyse.
Regards,
Raghu.

Application document created by IDoc

Similar Messages

Maybe you are looking for