ALEs/IDOCs doubt

Hello Friends,
I need suggestions for this typical issue
The business scenario is like that when we are creating purchase orders in one server it should create sales order in the another server automatically.
In the outbound it is moving without any error, and in the inbound side it is getting 51-status code after I am trying to post the idoc with respective process code.In the error it is shows the message like The material number for item 000010 could not be identified.
Thanks in advance
Ramu.

HI,
Adding further...
Although both Purchase Order & Sales Order use the same idoc type orders01, the data content will be different.
for example...the purchase order will have purchasing related data like purchasing organization, purchasing group, vendor etc...
however, sales order idoc requires the data like, sales organization, division, distribution channel, sold-to paty etc,...
You have to do the conversion of the PO idoc to an SO idoc(this has to be done after the inbound requirements for a sales order idoc is studied)...
Thanks,
Renjith

Similar Messages

ALE & Idocs doubts

Hi Experts,
I have big doubts in ALE & Idocs
1.There are lot of function modules to create idocs.
So how to find the relavent function modules for our
requirement.Is there any criteria for this.
2.When will we go to create idocs through BAPI,when we
have both systems(sending & Receiving) are SAP.
3.In INBOUND Idocs processing program,do we need to
compulsary use BDC to update the data in conserned
tables?
Advanced Thanks for your replies

Hi Murali,
u can findout the list of fm related to the concerned msgtypes in WE57 tcode.
We have standard inbound function modules wich takes care of process/updation in inbound side. (Se37--> search by IDOC_INPUT* ).
if those doen't suits to ur req. u can develop ur custom one and use BDC to update.
Thanks
eswar

Ale idoc doubt

hi,
when i send any material/customer from client 000 to 800.While,sending everthing goes ok till bd10,when i check in receiver 800 by tcode we02,it comes there also ok,but when i run tcode bd11/bd13 for getting the stuffs.one error comes
Could not determine recipients for message type DEBFET
Could not determine recipients for message type MEBFET
HOW TO CORRECT THIS.
Thanks,
Gaurav

Hi gaurav,
BD10 is used to send the material to the ale layer.
Then using bd11 in the receiving system u have to receive that material.
BD10 will not transfer the material to the receiving system directly.
Regarding ur error it might be some problem in ur customizing of the things.
Regards...
Arun.

Doubt in ale/idocs urjent

hi,
i have a doubt in ALE/IDOCS requirement is add a field to segment
in tcode BD53(reduce message type) after adding a field.
what configuration i need to do.

welcome to SDN.
Post this ABAP forum for quicker response.
ABAP Development
Regards
Raja

ALE/IDOC[custom table transfer]

Hi All,
I have a doubt regarding the type of programs used to post the idocs using ALE in the outbound process.
Please also tell me which program I will use to post a custom table of mine to another server using ALE/IDOC.
Please also tell me the procedure to do the same mentioned above.
Please help. Its a urgent requirement...........................
Thanks in advance......................................................

Hi Guru,
if you cannot use a standard idoc then you´ll need to create a custom one starting from the segment (WE31) where you can create an Idoc segment starting from your own Z table structure using the wizard.
Then you´ll need to also create the idoc type (WE30) and link the segment to the IDoc.
Then you´ll need to create a message type and link the message type to the Idoc type (WE81, WE82).
Then you´´ll use RFC "MASTER_IDOC_DISTRIBUTE" to populate the IDOC and send the data.
This is a sample code just to give you an idea:
DATA:
Z_SEGNAME(7) TYPE C VALUE 'SEGMENT',
Z_MESTYPE(9) TYPE C VALUE 'MESSAGE',
Z_IDOC_TYPE(8) TYPE C VALUE 'IDOC'.
DATA:
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*Reads data from Z table
SELECT *
FROM ZTABLE
INTO TABLE L_ZTABLE.
*Set the control data info required for the distribution
IDOC_CONTROL-MESTYP = Z_MESTYPE.
IDOC_CONTROL-DOCTYP = Z_IDOC_TYPE.
*Populate the IDoc
LOOP AT L_ZTABLE.
CLEAR IDOC_DATA.
IDOC_DATA-SEGNAM = Z_SEGNAME.
IDOC_DATA-SDATA = ZTABLE.
APPEND IDOC_DATA.
ENDLOOP.
*Deliver the IDOC as defined in distribution model/partner profile
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
    MASTER_IDOC_CONTROL          = IDOC_CONTROL
TABLES
    COMMUNICATION_IDOC_CONTROL     = T_COMM_CONTROL
    MASTER_IDOC_DATA               = IDOC_DATA
EXCEPTIONS
    ERROR_IN_IDOC_CONTROL               = 1
    ERROR_WRITING_IDOC_STATUS          = 2
    ERROR_IN_IDOC_DATA               = 3
    SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
    OTHERS                         = 5.
IF sy-subrc = 0.
COMMIT WORK.
ENDIF.

ALE/IDOC[custom table]

Hi All,
I have a doubt regarding the type of programs used to post the idocs using ALE in the outbound process.
Please also tell me which program I will use to post a custom table of mine to another server using ALE/IDOC.
Please also tell me the procedure to do the same mentioned above.
Please help. Its a urgent requirement...........................
Thanks in advance......................................................

hi,
u can do it using CHANGE POINTERS method.For this u need to do the following configurations.
1>WE81
2>WE31
3>WE30
4>WE82
5>SCDO
6>BD61
7>BD52
8>BD50
9>BD60
10>WE20
11>BD64.
First create an object in tcode -SCDO,there u specify ur tablename.
now the fields which are there in the ztable,in the further characteristics of the dataelement u need to check the check box CHANGE DOCUMENT HEADER.Now in SCDO u need to generate the upgarde program,the sap will generate four includes,u need to call them in ur program.
U need to write one FM ,where u need to use the FM's.
CHANGE_POINTERS_READ,
CHANGE_POINTERS_STATUS_WRITE.
Regards,
nagaraj

ALEAUD - ALE -IDOC

Hi,
I have doubt in ALE-IDOC. I would like to modify message that would get send from ALEAUD for which i am looking
for function module or available user exits.
Please let me know if u have any idea about it.
Thanks
Parag

Hi All,
We have the internal table u2013
This has to be as below
Hard code the Table lines till the end ( say 10 items ) u2013 end of the page = footer
The table lines are static 10 rows u2013 if table has 2 items only 2 items are displayed and the 8 rows will be displayed but blank and end of the page = footer.
In case 12 items are there u2013 display 10 items in first page and DO NOT DISPLAY FOOTER IN FIRST PAGE IN CASE line items are spreading to next page u2013
Second page will have rest two items and few more static lines as above and then FOOTER at last.
Over all the footer must appear in the LAST PAGE ONLY
Please send the details as soon as possible.
Thanks,
raghava

Reg:ALE/IDOCS

Hi Experts,
I have one doubt in ale/idocs that is , some idocs are accidently posted, how to solve this issue. at the same time how to avoid duplication of idocs. please send the answers.
Thanks & Regards,
N.Narasimha Rao.

I understand what you mean by "Duplicates", but the question that I have to ask is what do you mean by "accidentily posted".
The key thing to the ALE framework is the proper use of DB transactions. The updateing of the ALE status and message tables are combined in the same DB transaction as the actual buisness logic updates that are happening in your IDoc processing function. So what does this mean to you you're asking? It means that the implimentation of your update logic can sometimes cause the possibility of duplicates.
Certain types of updates are ones that cause issues, and these would be updates that are beyond your control when it comes to the DB transaction:
- BDC/Call Transaction - On these they have their own seperate DB transaction, so it is possible that the BDC can sucsesfully post a transaction and then when the logic returns to the IDoc processing function if something causes it to terminate before completing then it is possible that the buisness transaction is complete and your IDoc status has never been updated. Because the IDoc status has never been updated the same IDoc will get picked up for processing again.
- Calls to API functions where they contain a commit inside them or an option to include a commit and you don't supress it - Similiar to Call Transaction issues on this one that the buisness transaction can be commited before the framework commits its final status.
- Multiple transactions - Sometimes it is nesasary to call multiple APIs inside your processing function but they require commits in between them in order to work properly. An example of this could be first creating a customer master record and then creating a sales order for that customer. In this case a commit is required inbetween the two calls. In a case like this it is possible that half of your buisness logic has been executed and commited, the second part hasn't been commited and the framework hasn't commited the status. The requriment for the commit would be that the customer master API doing the update uses an update task and therefore the actual updates to the DB aren't executed until an explicit commit statement is executed (note also that the ALE framework sets update tasks to local mode so that it doesn't require the use of asynch update processes).
So, with these above things being issues when it comes to the DB transactions for ALE processing, what can you do to prevent them:
- For Call transaction issues there isn't much that you can do, becuase the DB transactions is out of your hands. The only solution I would recommend here is to not use Call Transactions. It is an old technology anyways and there are much better ways to do it usually by calling APIs.
- If the API you are calling contains a commit, you should look to see if there is an option for you to turn it off via an input parameter. If not then you will end up with some of the same issues as Call transaction but there is a technique that you can use to supress duplicates from posting since the DB transaction (unlike in Call Transaction) is actaully the same transaction that was started by the ALE framework, the technique is what I refer to as ALE Stages.
- If you require multiple API calls which require commits in between them then the solution that I have used many times is what I refer to as ALE Stages.
So how do you do ALE stages? The following is an overview of what you'll need to do:
- Create a new custom table as a copy of the INDX table (data cluster table). This table is going to be used for two purposes, one is to store information about what has been processed so far and secondly is to handle the passing of transient data if processing is restarted.
- In your processing function consider it as a number of stages (one for each transaction) and perform the following logic for each stage:
1) Use the import statement to read in data from the cluster table (Keyed off of the IDoc number). This contains information about what stages have been completed and also any transient data that has been generated by one stage and needs to be passed to another. You can use a complex data structre to store all of this information.
2) If the current stage has already been executed then skip this section of your processing logic. Otherwise execute it:
2a) Execute the API call
2b) Used an export statement to write an updated status to the data cluster table including any transient data that will be required for the next stage.
2c) Execute a commit
- After all stages are complete, do a delete on the record in the data cluster table. Important point though is to not do a commit. The reason that you don't do a commit is if there is a failure prior to commit inside the ALE framework that update the final IDoc status then you will have lost your stage status information and the entire IDoc would be duplicated again.
- By doing stages of this type you are creating sub-transactions that if the IDoc fails at any point then when it is reexecuted it will skip the parts that have already been done.
- The secret to this is that each stage is it's own DB transaction and includes the API call and the update to the stage status table together. The final deleting of the stage status is linked in with the overall DB transaction done by the ALE framework.
- In the case where you are using an API that has a commit embbeded inside it that you don't have control over, you can still use stages. The secret is that you need to update the stage status table prior to the API call. Even though it is done first it isn't commited until the API executes it's embeded commit. The only issue with this is that you can't depend on return values from the API as transient data to support the next stage becuase you have no way of writing it to the stage status table as part of the same transaction as the API update.
This is a failry high-level description of some of the things to look out for and how to handle them. The use of stages is something I've done a lot and is nice because if implimented properly it will provide a bullet-proof way to ensure that no part of your transaction will be updated twice. The main issue I find when I see developers try to implimnet this though is that they don't understand completly how DB transactions work and they end up with holes in their logic.
Hope this helps. If I've got some time at some point I'll post some specific pieces of code as an example of stages.
~Ian
Edited by: Ian Maxwell on Aug 3, 2008 5:43 PM

Ale/idoc reduce messagetype

hi,
i have a doubt in ALE/IDOCS requirement is add a field to segment
in tcode BD53(reduce message type) after adding a field.
what configuration i need to do.

requirement is already developed in reducemessagetype for message type is zdebmas
now i want add one field.
if add one field in BD53 next what i need to do.again need to configur patner profile?

Question on ALE/IDOC

Hi to all,
I have some doubts regarding ALE/IDOC can any one tell me answers to those question.
1. what is a process code? what is the purpose of process code?
2. what is a stand alone program?
3.How to handle to errors in ale/idoc?
4. ALE processes in asynchronous why?
5. How to run idocs in parallel?
6.What is a posting program
7. Can any one can send me one complete ALE/IDOC scenario with documentation ?
Please send me the answers to this mail id [email protected]

Hi guys,
I must thank every one of you for sending such quick and helpful responses. I bought the book "ALE, EDI and IDOC" from Aravind Nagpal and its a great book for beginner as well as for an expert. I have started practising ALE my PC by logging into 2 clients and it is working fine. I was able to send and receive the IDOC.
Thank you again.
This is a great forum,
Cheers,
Mahesh.
Edited by: Mahesh Kumar on Jan 21, 2009 3:32 PM

ALE/IDOC/BAPI/BADI/EDI

Hi,
ABAP GURUS
I am a new bie to SAP .Now I want to learn the following things :-
ALE
IDOC
BAPI
BADI
EDI
My doubt is that which should be learned first so that I can understand them more effectively. It may be possible that is not a question to ask but please guide me and also provide me some good links of ppt which gives me the complete overview of all these and the steps to use them.
Thanks In Advance
Bharti Jain

Hi Bharti,
EDI is Electronic Data Interchange, and is not linked to any technology, is just the definition of the communication of data using electronic equipment. ALE is Application link enabled, and is used by SAP to communicate data between systems, to build distributed systems, using electronic communication.
iDoc is a data format to send and receive data, then, can be used for EDI and ALE.
Bapi and Badi are programming tools, that allow to modify the data in the system, and also, a BAPI can be used to send data to other systems, but, in short, are just functions.
Regards,
Ivan.

Logical systems in ALE iDoc

Hi,
For exchanging data between two systems(not between two clients of the same system) using ALE iDoc , logical systems should be maintained in both the systems?
For eg: there are two systems, system A and system B.
i have maintained the logical systems as SYSA (for system A) and SYSB ( for system B) in the system A using the transaction 'SALE'. Should this need to be maintained in system B also?
Thanks & Regards,
Soumya.

Hi,
In both the systems you have to Define the Logical systems,
but in you assign only one to the client,
i.e. in system A you assign the Logical Sytem of of A to the Client in SALE
transaction the same goes for B.
and you don't need to create a distribution model for both the systems,
you can create it in one system and send it to the other system.
Regards,
Samson Rodrigues.

Upload data from legacy system to SAP through ALE IDOC

Hello All,
I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
Could you please provide a sample program for retrieving data for IDOC.
Thanks

Hi,
You can find the sample code in the following link.
Re: calling idoc_input_creditor
Regards
Sajid

Error in ALE-IDOC related to HR data posting in ECC 6.0

Hello People,
Upgradation done from 4.6B to ECC 6.0.
Here the data comes from the 3rd part s/w and then gets posted through a Z program which in tern calls SAP standard program " RSEINB00" and FM "IDOC_INBOUND_FROM_FILE" is used in this std program to post the data to the corresponding HR tables through IDOC postings.
ALE-IDOC Z program works fine in 4.6B but gives error in ECC 6.0.
Error in subroutine read_namtb for structure of infotype Message no. 5-109 Diagnosis An error has occurred in subroutine read_namtb for structure of infotype .
Procedure
Check the entry for infotype in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
As per the error message it seems that some table () needs to be maintained with some values, but this was working fine with the 4.6 B with current settings.
Is this error due to version change to ECC 6.0? What extra settings need to be done with respect to IDOC so that the posting program works fine without giving the stated error. Kindly let me know.
Thanks and regards,
Gaurav Joshi.

Please keep in mind ECC 6.0 is an UniCode based system.
as 4.6C was not,
did the Z-program have been tested before in the current environment?
Some special functions (keywords hints ...) are no longer supported after the upgrade.,
this was shown during the upgrade in the unicode migration tools
For sure all the own programms needs to be verfied, after an upgrade.
commonly this should be done
in the quality assurance test to avoid touble in production.

Error while crating Sales Order using ALE-IDoc?

Hi all,
I have developed an ALE-Idoc interface to create Sales Order automatically When the user created a purchase order. It is working fine since past two months.
But now one SO is not created and the error message in Inound idoc is 'Sales Area not defined' message no V1316.
The material used in Po creation is created recently and using first time . i am expecting the problem is with in this material because the PO's created based on other materials is still creating the SO successfully.
Please help me in solving this problem?
Thanks,
Vamshi.

Hi shan ,
Thanks for you reply. The sales area for customer and vendor is maintained in VOE2 and taking correctly for other materials except for the new material.
Also in Inbound IDoc which contains the error is having correct sales area in it's segment . But showing that in the error message as 'sales area & & & is not defined' here the sales area is wrong one it is dispalying.
so please help me on identifying the problem?
Thanks,
vamshi.

ALEs/IDOCs doubt

Similar Messages

Maybe you are looking for