Configure ACCONF idoc in XI

Hi,
We are using ACCONF idoc as an acknowledgement idoc for the inbound INVOIC idoc. But, the ACCONF idoc doesn't reached to the receving system eventhough it is created and the status is 12.
Please suggest me how to send the ACCONF idoc to receiving system.
Thanking you,
Regards,
Krishnaraju.

Hi KrishnaRaju,
Our requirement is also to send the status of inbound INVOIC idoc in ACCONF.
I'm stuck as to how this needs to be configured. How does ACCONF get triggered for INVOIC02 idocs with process codes ( MM- INVL and FI -INVF ) ? How was this configured in your system? Your help is much appreciated.
Thanks.

Similar Messages

How to configure ALE/IDOC in nace for V3.

Hi,
Please let me know how to configure ALE/IDOC output type in Nace and how to configure the message outputs.
I require the steps to configure the above.
Screen shots will also be helpful.
Regards,

Hi Somya,
I have a little manual that explain how to create an outbound Idoc from a message class (for invoice).
But it is in spanish, if you want give me a email address and I'll send you.
Rgrds,
Francisco Castillo

IDoc output type not getting configured in IDoc-File scenario

Hello
I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
1] Created output type
2] Created partner function as EDI LS for this output type
3] Configured RSNASTED as Processing Routines for output type
4] Included this output type in the Header output procedure
5] Configured XI system as the partner in partner profile with appropriate Message control
Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
I checked in SPRO but could not find such flag.
Does anyone had came across such output type configuration.
Thanks in advance.
I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
Regards
Rajeev

Hi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar

Integration Directory configurations for IDOC - XI - File

Hi all,
I have a scenario as above: IDOC-XI-FILE
The IDOCs come from an R/3 system - NHGDDBS01.
I've configured 2 BS:
1) BS_NHGDDBS01
-> TS: NHGDDBS01, type: WebAS ABAP
-> SWCV: BASIS 6.20
2) BS_DEV1_NAUTICUS_OOTS
-> TS: TS_DEV1_NAUTICUS_OOTS, type:Third Party.
-> SWCV: SWCV_DEV1_NAUTICUS_OOTS, type: Third Party
-> PDT: PDT_NAUTICUS_OOTS
With this setup, can someone help me by showing me how to configure the Integration Directory in order to receive IDoc from R/3 (nhgddbs01)?
Please help.
Thanks.
Ron

> This is known issue.....Check the below
> steps.............
>
> Go to XI system ->and IDX1 transaction.. And check
> the port number + RFC destination is given correctly.
> this should point to SAP system ..
> Check thsi RFC destination is having all the entires
> and test connection success
>
> And the port should have the naming convention
> SAP<System Id>.
>
> ........................Check this SAP Note -940313
Hi,
I followed the SAP Note.
The SAP System ID is DV1.
I've configured IDX1 with the following port:
Port: SAPDV1
Client:108
Description: <blank>
RFC_Destination: PI_001 (This RFC destination points to DV1, despite the naming. Connection test is successful)
I recreated metadata on IDX2:
IDoc Types: ZPATINFO
Source Port: SAPDV1
IDoc Types: ZADMINFO
Source Port: SAPDV1
However, when I test the message from R/3 using WE17, SM58 on R/3 it's still showing the error:
Transaction IDX1: Port SAPDV1_108, client 108, RFC Destination error.
May I know where did this error occur and how to rectify this?
Please advise.
Thanks.
Ron

Dynamic Configuration for IDOC

Hi,
Whenever an IDOC is send from SAP R3 system to PI (SAP R3 -> SAP PI -> Target), we get an additional node of Dynamic Configuration under the SOAP Header in SXMB_MONI.
Why is this happening? Does this happen for all the versions of SAP XI (PI)?
This issue does not occur when the IDOC is send by SAP PI to SAP R3 system (Source --> SAP PI --> SAP R3)
I am using SAP PI 7.1.1
Thank you,
Pankaj.

Hi,
Why this is an issue for you?
I am trying to send IDOC from SAP System to PI system.
Ideally there should be no DynamicConfiguration step under SOAP Header folder in SXMB_MONI (I tested a SOAP -> PI -> FILE and the Dynamic Configuration does not come); unless and until we make use of the ASMA properties (UDF/ Module). Is this understanding correct?
For example, if I send an IDOC i get the below details in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<SAP:DynamicConfiguration SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">SAPPI</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">SAPPISYSTEM</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPECC</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">SAPECCSYSTEM</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP"/>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">Z_VALIDATION_ACK01</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">Z1VALIDATIONACK</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
</SAP:DynamicConfiguration>
Is this behavior as expected?
Thank you,
Pankaj.

How to configure Sender IDOC adapter

Hi could someone pls guide me on the steps that i need to take to configure IDOC sender adapter..
Are the steps for Sender and Receiver IDOC adapter same other than the fact that sender idoc adapter doesn't need a sender communication channel.
Regards,
Ashish

hi Goyal,
Just check out this link.
How to Configure IDOC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Regards
Sachin

Port Configuration EDI/IDoc

Please anybody can explain me in detail Port Configuration for EDI/IDoc(T Code WE21).
please explain how can i create new port.
it's urgent please.
thanks
RP

rp
check the following links
http://help.sap.com/saphelp_47x200/helpdata/en/af/7e844367c24d4a950df3205052769d/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm

XI Configuration Problem - IDOC

Hi, guys
I am trying to configure IDOC transfer(HR Master Data) between ECC5 and XI 3.0.
I think I did all the configuration. But when I am trying to test by distributing HR Master Data, it shows the following error in sm58.
No service for system SAPPRO, client 100 in Integration Directory.
Can anybody help me with this problem, please?
Thank you

Hi,
check the port in IDX1 if you have with convention SAP<SID>
all steps to do that are in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
 can anybody tell me the steps how to configure an Outbound IDOC.
 It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
 if not anything else will also do.
 Kindly give me steps in detailed. Since i have never done this. Including
 distribution modle (BD64). in which case it generates the Automatic Partner
 profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
 a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
 b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
 c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

CCMS - issue configuring new IDoc monitor template

Hi,
we wan´t to create a new CCMS IDoc monitortemplate in our central ALE configuration system and define all relevant remote SAP System and transport the complete template to the Solution Manager System.
We wan´t to customize the template in the ALE configuration System, "not" in SolMan.
These are the steps i´ve already done.
1. create new MTE´s by transaction BDMONIC2
2. customize the new MTE´s by tr. BDMONIC
3. create a new Template in RZ20
4. create a new Monitor for the new TEMPLATE in RZ20
5. after some minutes (the new created MTE´s are available for configuration)
First question. Why i have to wait some minutes to see the new MTE´s in the new monitor ?
anyway,
the monitortemplate for my own system(template creation system) is working fine.
6. Now i´ve created new entries to monitor remote SAP Systems in RZ21
7. I can see the new SAP Systems in my new TEMPLATE in RZ20
8. I would like to use my created MTE´s for every SAP System. Transport all MTE´s and configuration to the relevant SAP Systems.
9. I can see all entries in BDMONIC2 and BDMONIC in the remote System ...
... but I can´t see the new MTE´s in RZ20 in the remote System and
I can´t see the the new MTE´s (for the remote system) in my new TEMPLATE in the ALE configuration System (where the remote system is assigned).
note: I saw that a new MTE creates a new alert class in RZ21.
This class is filled in the template creation system(ALE configuration) but not in the remote system.
Any ideas what is going wrong here ?
thx,
Gordon
Edited by: Gordon Breuer on Jul 30, 2009 2:28 PM

Hi,
check this links:
http://help.sap.com/saphelp_nw04s/helpdata/en/9d/df1241c738f423e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/forums
Regards,
Spandan

Ale configurations for IDoc?

hi..
What are the ALE configurations need for an IDOC?
bye.

Hi,
Perform the following ALE configurations
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.
Also gothru this Blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points

Configuring ale idocs

Hi friends ,
I want to know the steps that i need to do before sending an idoc from on sap system to another sap system . Say i am sending an standard idoc invoic01 from from one clientxxx to another clientyyy. What is the procedure ?
Thank you ,

various steps involved are like this:
Define RFC destination(SM59)
create new r/3 type destination provide necessary things(password,ip, etc)
Inbound:
1.Create IDoc type (WE30) Client independent
2.Create message type (WE81) Client independent
3.Link message to IDoc type (WE82 & BD69) Client independent
4.Maintain object type for message type (BD59) Client independent
5.Configuring the Distribution Model (TX:BALE ALE -> Distribution customer model -> Maintain customer distribution model directly)
6.Distribute customer model (BD71) Client dependent
7.Distribute Model (BD71) Client dependent
8.Maintain sending system partner profile (WE20) Client dependent
9.Populate & distribute IDoc using ABAP
Outbound:
1.Execute processing Function
You can refer these links for better understanding:
http://www.sapgenie.com/ale/whitepaper.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
regards

How to configure Change IDOCS

Hi Experts,
For one of my requirement I need to send IDOCS whenever few fields in the delivery document is changed(repetative IDOC for repeated changes) using delivery IDOC typr DELVRY03. Please suggest me the possible solution and configaration for the same.
Regards,
Emaya

Hi,
Go through this hope u can understand.
Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks

Idoc ACCONF configuration

Hi friends,
We have inbound INVOIC message type configured in our system to post vendor invoices for both MM ( process code INVL ) and FI ( process code INVF ).
Upon the idoc posting is complete the requirement is to send a ACCONF idoc back to the sender with the status on the invoice idoc posting. I'm having trouble finding any information on what needs to be set-up to trigger this ACCONF Idoc type ACCONF01I.
Can anyone help with this?
Thanks in advance for your time.

Hi,
I am not sure if this is the best way how to create your IDoc but you can try to use Business transaction event. There is event for posting FI documents. You can try to use this event to call FM which will generate your IDoc. Another possibly better way might be to define your IDoc as output message for FI document. Hence SAP will generate it automatically after creating FI document. You can find some examples of setting IDoc as output message in transaction NACE. Look for output types with word EDI in description. I would try the second option first.
Cheers

Idoc ACCONF trigger point

Hi friends,
We have inbound INVOIC message type configured in our system to post vendor invoices for both MM ( process code INVL ) and FI ( process code INVF ).
Upon the idoc posting is complete the requirement is to send a ACCONF idoc back to the sender with the status on the invoice idoc posting. I'm having trouble finding any information on what needs to be set-up to trigger this ACCONF Idoc type ACCONF01I.
Can anyone help with this?
Thanks in advance for your time,
Hitaishi

Check BTEs 00001025 or 00001030
Regards
Vinod

Configure ACCONF idoc in XI

Similar Messages

Maybe you are looking for