Need Flat file for Message type DELINS

Hi Experts,
It possible to see the flat file for the Message type DELINS ,, If needed means please say how it can view..
Advance thanks..

>My need is to convert the EDI format into SAP.
As far as I know EDI can be read by SAP as Idoc directly without conversion. At least I would try this.
I checked in WE20 /partner profiles/ for outbound parameters there is a tab called 'EDI standards' and here you can define the EDI parameters. However there is no such tab for inbound processing.
What I would do /using transaction code SALE/
- define logical systems
- assign the received to the client
- create RFC port for Idoc processing
- create distribution model with the correct message type
- create port as file
- define or generate partner profiles
Try to upload sample files via transaction WE19 or WE16.
You can try to debug the inbound processing and write a program based on that, which could be scheduled as a background job.
I had a program doing similar, but it was another message type and it was XML based, however the FMs I used are the following:
'EDI_PORT_READ' - read port definition
'EPS_GET_DIRECTORY_LISTING' - get the file names in the dir
'EDI_DATA_INCOMING' - process idocs
Hope it helps.
Peter

Similar Messages

Can not generate one xsd file for message type in xi

Dear Experts.
I am not able to generate one XSD file from message type from XI 3.0, When i select message type and go to XSD tab then click on export xsd to file, it is generating two xsd files MainSchema.xsd, Schema1.xsd into one zip file, but i need only one xsd file to import it into MDM.
Could you please help
Thanks and Regards.
Sravya.
The following are the two files. MainSchema.xsd, Schema1.xsd .

Hi Harsha,
Thanks lot for the immediate response. Appreciate it.
Now I am able to generate the one xsd with your inputs , but i am not able to load it into mdm with out any changes in the generated XSD from Message Type. the below is only the original root tag, where modification required.
Original Element : MDM_CUST_MASTER_FILE_REQUEST_MT
==============
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:abc.com:MDM_Customer_Master_ECC" targetNamespace="urn:abc.com:MDM_Customer_Master_ECC">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
etc.
Case :.When i modify the above element as below with out xmlns, targetNamespace
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
I can import xsd into mdm with the above modification.
The generated XML out put File from mdm is having message type tag like below
?xml version="1.0" encoding="UTF-8"?>
<MDM_CUST_MASTER_FILE_REQUEST_MT>
<CUSTOMER> </customer> ...
note: no namespace for message type
Result:
1.When i send this xml file into XI it is failing in message mapping because it doesn't have namespace attached to it and failing in message mapping.
Finally i need your help to generate the xsd or data file like below to avoid mapping problem in xi.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MDM_CUST_MASTER_FILE_REQUEST_MT xmlns:ns0=urn:abc.com:MDM_Customer_Master_ECC>
Appreciate your help.
Thanks and Regards.
Sravya.

I need Flat file

Hi,
Experts,
I need the flat file for these T.codes
FEBC
S_PLO_09000467
FF_5
FEBP
FEBA_BANK_STATEMENT
Table & field wise
Thanks & Regards,
Sreedhar.

Look at <a href="http://www.stylusstudio.com/edifact/D96A/FINSTA.htm">Financial statement of an account message</a> for the full information
But better ask your bank.
Regards

How to design Flat file for loading attribute dimension in a planning application

Dear Gurus,
I have a requirement to extract attribute dimensions from an essbase application and load it to another planning application. I have a dimension called Program and two attribute dimensions Sales Manager, Accounts manager associated with Program dimension in Essbase application. I will Extract these dimensions using Essbase outline extractor. After Extracting the attribute dimensions I have to load these dimensions to planning applications using outline load utility. Kindly guide me how to design the flat file for loading attribute dimensions in planning application.
Thanks and Regards
SC

You could dig through the docs and try to figure out the file format manually, or you could do this the easy way. Simply use the Outline Load Utility to export your attribute dimension from Planning. The export file format is the same as the import file format. You might have to manually add a couple of test members to your attribute dimension so that your export file has some content. Then simply update the file you exported, and import it.
(I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
Hope this helps,
- Jake

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.

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.

Custom segment does not exist for message type Debmas_cfs

Hi,
I have created a custom segment YEXTRA for basic type DEBMAS06.
I have done the configuration in We82 and We20.
I have implemented the segment in User Exit "EXIT_SAPLVV01_001". Now when I am executing the TCODE BD12 then it is creating the Idoc with custom segment. But when I apply the filter on sales org in BD64 then it starts giving me error that " Segment Y**** does not exist for message type DEBMAS_CFS.
Kindly suggest if I need to do some other configuration also.
Thanks.
Regards,
SAurabh

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

Message no. B1003""Could not determine recipients for message type ACPJMM""

Hi All,
While posting GR in MIGO, an error is showing. I am attaching the error description.
""Could not determine recipients for message type ACPJMM""
Message no. B1003
Diagnosis
An IDoc of message type ACPJMM 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.
Yesterday it was not coming and GR was getting posted.. I was doing configurations for CIN and day before yesterday everything was done,all the registers were getting updated. For that I did many customisation in SPRO. I did settings in tax ion goods monement. and in Material master to assign screen sequence for foreign trade data screen. Is any customozation triggerring IDoc? Earlier also this came, that time we got client copy, but the problem is recurring. Its very urgent as we are going to transport SPRO settings to production.
Solutions will be rewarded.
regards
B Shar
Edited by: Ian Wong on Jul 4, 2008 4:48 PM

Hi
If you are not working with ALE & this message comes, then somone has mistakenly activated ALE linkages for IDoc Output in Accounting.
if you want to keep this active & go forward, you need to complete the Distribution model customizng in BD64.
Thanks & Regards
Kishore

Too many recipients found for message type ORDERS in the ALE model

Hi all ,
please help me to solve this issue .
i done with ale settings .
orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

> orders message type is used in 2 different model view for 2 different systems
do both of them carter diffrent needs or is it the same idoc which is being sent to diffrent systems?
if yes, then use a single model view with noth receiver systems defined in it.
if not, i would suggest, copying the standard idoc and create a zidoc and then use different ones for diffrent receivers....
or u can use diff versions of the orders message type...
say orders05 for one.... receiver and orders02 for another one....
hope this helps!!
Cheers!!
Sidharth

Too many recipients found for message type (Distribution model)

Hi,
I wanna send Dilvery note using message type DESADV from a SAP system to another non-SAP System.
I have Created port partner profile and distribution model.
But the Problem is the same message type DESADV is used to send Dilvery from SAP System to another SAP Client.
Idoc getting failed and throwing error stating Too many recipients found for message type DESADV in the ALE model .
I am sure we can create the more than one recipients for same message types. I have done it some time back. Any help highly appreciated.
Regards
Raj

This message pops up when SAP can't identify how to distribute the IDoc based on the settings in BD64. Take a look at the settings there, most likely you'll need to add a filter.
The big ALE/EDI/IDoc book suggests that the same IDoc may be distributed to 2 different systems but specific details are not clear. It seems that one system should be configured first (it does mention a need to use a filter) and then somehow menu Edit -> Model View -> Distribute should be used.
I've never done it myself though and have only run into that error when I missed some filter settings in BD64. Hope this helps.

Too many recipients found for message type in the ALE model

Hello Friends,
Please help me in solving this error. I have a Outbound sales order confirmation ORDRSP .
In the distribution model i have defined the sender receiver and message type clearly...
But in va01 after creating sales order extras ->Output->Hearder --->Edit
Output type-- BA00
medium --ALE
Dispatch time : Send Immediately
I am getting a error -
Too many recipients found for message type ORDRSP in the ALE model
Message no. B1130
Diagnosis
In the ALE distribution customer model several recipient systems for IDOCs with message type ORDRSP and filter object type 'KUNNR' with value '100' have been modeled from this system, but only one recipient system is allowed.
Procedure
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
Please help me in solving this error.
Regards,
jeevan

Hi Jeevan,
In BD64, the said problem occurs, since the message type ORDRSP will be configured to different Logical System.
Since you are creating sales orders & Output type, system doesnt knows, to which Logical system, it has to be sent since the Message type exists more than once.
select Your respective Logical System where the Outbound Sales Order Confirmation ORDRSP has been created.
Under the node ORDRSP, add the filter group for Customer.
Double click the Filter group and add the respective Customer No.s to whom the Order confirmation needs to be sent.
Then create Sales Order Confirmation & Output type. Data will be passed(IDoc) to the respective Customer(where the customer no.) exist in the filter.
Hope it solves your Issues.
Regards,
Anbalagan.

ALE for message type BATMAS

Hello
I am trying to generate IDocs for a copy of the message type BATMAS and have added some custom fields to this new custom message type..
1. I have created BD52 entries for this new custom message . But starngely the IDoc created is for message type BATMAS instead of the new custom message type in WE02. I am executing BD21 for the new custom message type . I have checked BD64 and partner profile settings for the new custom msg type. I have activated change pointers for this new message type in BD50 and BD61.
2. I added a new field MCHA LVORM to the fields in BD52 . But the IDoc is not genearted whenever we change deletion indicator(IDoc).. Its creating the IDocs for changing all the other already existing fields.
I'd appreciate any suggestions/help.
Thanks
V

Hi Ravi;
Just so I understand you, an IDOC was successfully created in ECC and sent to an outbound system. Your outbound system, in this case is PI, which is acting as middleware for your ALE. Now you have an error in PI and you can't get it sent to EREC.
I know people don't like getting questions answered with other questions, but why are you using PI in this scenario? Every ALE scenario I've utilized uses HRMD_ABA directly from ECC to the target system (not with a middleware piece included). In WE20, what would be the harm in changing your receiver port to your actual EREC system? Do you have some kind of business logic being executed in PI converting IDOC field values?
If you think you must use PI, then in sxmb_moni, it would be interesting to know the error message for the IDOC there. However, I think it's entirely likely you don't need to use PI at all and could just use a direct RFC between ECC and EREC.
Good luck,
Chris

Extracting from flat file for testing inplace of ECC(r/3)

Hi Expert,
Please help me out and give me your suggestion.
We are creating a custom table in ECC it is under progress.
I would like to create infoObject, transformation, DTP and Cube and create queries with loading info by flate file. Later on connection whole provider to table.
Give me suggestion is ther any problem for this Or any good opinion.
Thanks in Advance

Loading from a flat file for testing has worked well for me. We recently wanted to test an ODS object, but I didn't want to create a custom extracter until we knew if the ODS object would work for us. So under my infoSource I created a quick infopackage that pulled some test data from a flat file. We've loaded test data into cubes before. Only problem that I ever had was when I used Excel to create the flat file. Excel wants to truncate leading zeros. 0calmonth for example needs to be loaded as 072007 not 72007.

USER EXIT for Message Type PCROLL

Hello Gurus ,
My requirement is that i need to convert few fields for Message Type PCROLL (Basic type GLDCMT01) before sending it to other system by ALE . Can somebody help me out which user exit should be used .
Many thanks for your help in advance .
Regards,
NK

For future reference in case anyone is trying to do this, we were not able to find a suitable user exit to enhance BENEFIT3 IDoc, so we put in an OSS note and received the following response:
"...currently there is no user exit/Badi in SAP Benefits Administration
to enhance IDoc BENEFIT3. Such functionality is indeed missing in the
system, which means that you will need to submit a development
request to enhance the system in this respect in a future release."
Anke

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

Need Flat file for Message type DELINS

Similar Messages

Maybe you are looking for