Trigger inbound BAPI IDOC for message type ACC_GL_POSTING

I configured our SAP system for inbound GL postings -- message Type ACC_GL_POSTING process code BAPI. I successfully tested all the configuration pieces using WE19.
So how do I trigger the inbound process from my external non-SAP system. I would prefer not create a flat file that is passed by calling EDI_DATA_INCOMING. I also do not want to use BAPI_ACC_GL_POSTING_POST. So what RFC enable FM can I call to pass data and trigger the IDOC generation and processing? Is there anything standard?

I will use the standard RFC enabled function module IDOC_INBOUND_SYNCHRONOUS. No custom abap development will be needed.
Message was edited by:
David F

Similar Messages

How do I execute IDOC for message type LOIPRO

How is it possible to execute IDOC using message type LOIPRO which I have configured with change pointers? Change pointers are using object ORDER.
I am looking to only generate IDOC for production order changes / updates that meets the criteria set by the change pointers. If something in the order changes, but that field is not being looked at by change pointers, I don't need IDOC to pick up that order.
I don't want to have to run RCCLTRAN or RCCLORD on a scheduled job. Only need to have activity if change pointers are activated. Am I going down the wrong road using LOIPRO ?

Hi Bob,
Could you please guide me through the process of creating/triggering a change pointer based LOIPRO? Your help much appreciated.
Tabraiz

Generating an IDOC for Message type PROJECT in Change pointer?

Hi,
I am trying to generate an IDOC. for the Message Type PROJECT(Actually this msg. type PROJECT is for BAPI method) in CHANGE POINTERS but it is possible Error is coming, is there any other method to use the message type in change pointer technic.
Thanks,
Vinayak,
Message was edited by: vinayaga sundaram

Hi Vinay,
Had a similar requirement few days back..
What we did was to do a multimapping of 1:N where N = N1 and N2, N1 is the Idocs which you are doing today, N2 is the set of invalid records...
Now we have written this as a file and then created another interface which will pick the file and based on the name of file we decided the To address. We have used mail package and this interface (file to mail ) was made as a generic one so that it can be used across many interfaces...
filename and To address relationship was maintained as a value mapping in ID... You can have a thought of this approach and try to send the invalid records as a mail rather than alert.
Regards
Suraj

Outbound IDOC for message type PAYEXT

Hi,
I am trying to send a IDOC from my SAP system to a EDI vendor. For one particular vendor in segment E1IDKU3 field PAIRZAWE (payment terms) is mot coming, thought this data is been maintained in Vendor Master Data.
In Segment E1IDKU4 field FCAREGUL is also missing for which also there is a data maintained in Vendor Master.
Can anybody explain why this is happening.
Also, which is the FM or IDOC creation-processing program for this message type.
/Manik

Hi Manik,
Your function module to process the IDOC will either be FI_EDI_PAYEXT_PEXR2001_OUT or FI_EDI_REMADV_PEXR2001_OUT depending on whether you are doing a remittance advice or payment advice.
In include LIEDPF1T, subroutine FORM FILL_SEGMENT_IDKU4 USING DOC_TYPE, you will find the following code. This tells me that your E1IDKU4 problem is also related to your instruction key settings. Check this table and see what is wrong.
      IF NOT T015W IS INITIAL.
        CASE T015W-DTKVS.              "Gebührenregelung
          WHEN '00'.
            E1IDKU4-FCAREGUL = Q_FCA_GETEILT.
          WHEN '01'.
            E1IDKU4-FCAREGUL = Q_FCA_Z_PFICHTIGER.
          WHEN '02'.
            E1IDKU4-FCAREGUL = Q_FCA_Z_EMPFAENGER.
        ENDCASE.
      ENDIF.
If it helps, please reward and close the thread.
Srinivas
Message was edited by: Srinivas Adavi
By the way what is Sardinians?

IDoc for message type WMPIHU (Creating Pick HUs)

Hi,
does anyone know the structure of the IDoc for the WMPIHU message type?
Is specified by the WM-LSR interface but it's not listed into the "Interface Between the WMS and External Systems" document.
Thanks
Michele

IDOC Bais Type is WMPHID01.
segment type E1LPHUX. you can check the stracture as of your system version in WE31.

Error monitoring through workflow for idoc with message type ORDRSP

Hi All,
Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
Regards
Suchandra

Hi All,
Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
Regards
Suchandra

ALE with BAPI; No recipient found for message type

We have to send sales activities from an ECC-system to CRM and tried to do this with message type SFADPSA and Idoc SFADPSA01.
When adding this message type to the distribution model (transaction BD64) we got the SAP-message to use a BAPI instead: IF1037SR with method RECEIVEPARTNERSALESACTIVITY. So we did.
To trigger the Idoc, we customized an output type, with transmission medium ALE, program RSNASTED and processing ALE_PROCESSING.
When processing the output type we get an error B1 129: "No recipient found for message type SFADPSA in the ALE model".
Analysing the error I found out following: during processing (RSNASTED, ALE_PROCESSING) function module MMODEL_INT_VALID_GET is called. This FM only looks into table TBD05, in which no entry for message type SFADPSA is found.
However, also function module BMODEL_INT_VALID_GET exist, searching table TBD06.
This table does contain an entry for the above BAPI and method and would not lead to an error message.
Obviously this last FM should be called, but this never happened...
Has anyone a clue?
Do we use the correct processing code?
Another message type to use could be SFADSACTIVITY, but this message type has no Idoc type assigned.

Hello Wolf,
This error message come while determing the distribution channel.
This error come from one of below includes. Can you please put a break point and swich update debugging on and check whether the program is populating reuqired parameters to determine the distribution model. by doing this you can understand what is going wrong....
LBDMOU17
PCHEAF01
PCITEF01
RBDSECOP
RBDSEGLM
if you are not able to check this let us know..
Regards
Naresh

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

LSMW: ALE/IDOC, getting the Create a partner profile for message type

Hi Gurus,
In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
when i'm generating the idoc in the 13th step, its posing the information message stating that:
Create a partner profile for message type 'ZEMP_MSG'
In partner profile i already assigned the message type .
How to solve this issue, <inappropriate urgency removed by moderator>
Thnks&regards,
sree
Edited by: Thomas Zloch on May 13, 2011 9:55 AM

This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

Inbound problem for message type WPUUMS

Dear all,
I want to receive the IDOC data for message type WPUUMS from a java server. Currently i am working on sample values for segments
E1WPU01
E1WPU02
E1WPU03
E1WPU04
E1WPU05
E1WXX01
I am facing problems in passing the correct values .
Its throwing a error message status 51.(Application document not posted) IDoc not fully processed.
can you help me with some dummy data for all the fields in the above segments.
reply ASAP
regards
arun

You have to analyze where exactly the problem is.
There are several reasons why the Idoc did not post:
1) The Data you are sending to post document may be wrong. You may have to validate against valid data in Database.
2) Thre may be some mandatory data which you are not passing through IDoc (Idoc data may be missing).
It is not possible to answer a generic question like this with perfect answer.
Best way is to debug and find out why exactly the problem is, if you know the error message (you may see it in Status record of this IDoc).

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

Diff bet IDOC and Message Types.

What are the difference between IDOC and Message types.
Diff between MATMAS01 ,MATMAS02 and MATMAS03

IDOCs:
- IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
-Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
IDOC TYPE IS AN INSTANCE OF IDOC
Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not a local object type , it is transportable.
For different applicatons we have different MESSAGETYPE.
example:
APPLICATION MESSAGETYPE
MATERIAL MASTER MATMAS
VENDOR MASTER CREMAS
CUSTOMER MASTER DEBMAS
MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
REWARD ME IF THIS IS HELPFUL

Could not determine recipients for message type HRMD_B

Hi,
I am getting below Error in SRM when transferring Org Structure data from HCM system to SRM system in a Idoc. I am using Message type HRMD_ABA and not HRMD_B. I didn't maintain Distribution model for HRMD_B. But in my IDOC status I am seeing below error message for Message type HRMD_ABA Inbound to SRM.
Only I am seeing HRMD_B message type in transactions WE81 and WE82.
Any idea? I appreciate your help.
Could not determine recipients for message type HRMD_B
Message no. B1003
Diagnosis
An IDoc of message type HRMD_B 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,
Shears

Hi Shears
Did you find soulution to your issue ??
thanks
Anup

Partner profile for message type.

Dear All,
I am using bapi in lsmw for data conversion.
I am getting error in 13th step of lsmw, ie, when I execute Start Idoc Generation, it's saying,
Create a partner profile for message type - MATERIALVALUATION_PRICECHANGE.
I already created a partner profile and assigned in the initial screen of lsmw.
Kindly let me know where I am missing.
Thanks in Advance,
Ranjan

See if any of the follwing helps:
1. The port used in the partner profile should be a file port, not tRFC.
2. The checkbox 'Unicode Format' for the port LSMW in WE21 should remain unchecked.

Wrong Partner Type in IDoc with message type REMADV

Dear all,
We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
Does anyone know how to change the partner type from the Idoc generationg?
Many thanks,
Ronny

Hi,
Welcome to SDN.
Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
Regards,
Ferry Lianto

Trigger inbound BAPI IDOC for message type ACC_GL_POSTING

Similar Messages

Maybe you are looking for