How to create customer master IDOC

i need to create outbound IDOC for sales order
i need suggestions regarding this.

Hi,
Are you first familiar with the ALE configurations.so that you can start with sending the Sales Orders.
Where there is different ways of sending IDocs.Please let us know what exactly is your scenario.
Regards,
vamshi

Similar Messages

How to create customer master data for walking customer in retail

hi experts !!!!!!
for retail industry e.g books trading industry
how to create customer master data for walking customer in retail
its dummy or one time customer
if i create one time customer then same customer number can i use for every new order and every new customer how ?????
thanks

Dear Hanumant,
As per my view,,
You can use one time customer functionality to full fill your requirement.
When you create sales order with one time customer system take you to the customer data maintanence screen through that you can maintain the one time customer data.
Same one time customer number you can use for every new order through maintaining different data.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Dec 19, 2008 6:08 AM

How to find - Customer Master IDoc was created Manually or by Change pointe

Hi all,
I have an IDoc(Customer master) number (which I have taken from the payload in SXMB_MONI). I would like to know whether this has been created by a user manually(BD14) or by a change pointer.
Please help.
Cheers
danus

Hi Vardharajan,
Yes I agree with you. What I mean by IDoc created by change pointer is - 'IDoc generated because a change(pointer) is tracked by the system', in other words, due to some change made to the data.
As you know, the other option of creating IDoc is by BDxx transaction. This option is usually used to push (unchanged) data.
So in essence, what I am interested to know is , has the IDoc been generated because someone made a change using say, VD02 / XD02 or pushed the data manually.
Please do ask, if anything is not clear.
cheers
danus

Create customer master record with reference to existing division

how to create customer master record with reference to existing division?

what type of reports sd consultant configure in implementation project?and in supporting project?

How can I include Customer Hierarchy in Customer master IDoc -DEBMAS06 ?

Hi,
I am generating Customer master IDoc using basic message type DEBMAS06. But when I include customer hierarchy data while creating customer master, it is not included in any of the segments. The segment containing the data from KNVH is not included in standard.
How do I include this hierarchy data in the IDoc? If I create a segment, under which basic segment should it be included and how to update the data in the segment?
Can anybody help?
Points assured.
Best Regards,
Rajendra

Hi
You can use LSMW :-
1) Create a project , sub project and an object.
2) execute it from 1 st screen to enter the object.
3) You will find proces steps.
4) In Maintain Object Attributes choose Program Name RFBIDE00.
or I-DOC or the way you want the input to be.
5) You can proceed from there following the instruction..

File to IDOC scenario: Create customer master and then return customer no

Hi all.
I have a scenario to pass xml file to sap XI to generate IDOC to create customer master in SAP. My problem is that I need to return customer no. created in SAP from IDOC. Is there any solution to do this? Someone told me that BPM could be used for doing this but I don't know the steps.I have no problem in create customer master in SAP. My only problem is how to return customer no. Any help would be appreciate. Thank you.
Best Regards,
Pavin

>>u can use synch-Asynch bridge using BPM
This can not be done via sync-async bridge.There are 2 reasons for this
1.He has file adapter as sender and that doesn't support synchronous scenarios.
2.He has standard IDOC as receiver.there is no way you can fetch customer# from IDOC without writing a custom program,Thats why i said he need to either use RFC/Proxy or do some custom development.
Thanx
Aamir

IDOCS: How to Create Address Master to tranfer TPSLOC01 Idoc

Hi Gurus,
We are tranferring Location Masters like Customer, Vendor, Plant through TPSLOC01 IDOCs from SAP ECC 6.0 to Third party Trnasport Management System.
How to create Address Master Data (TRMTYP-AD) separately like Customer Master (TRMTYP-CU, Vendor Master (TRMTYP-SU) so that we can tranfer the Address Master Data through TPSLOC01 IDOC.
Thanks&Regards
Sreekanth

Hi All,
This is closed as we have transferred only General data of the customer.
Thanks for all.
Sreekanth

How to transfer Customers to GTS immedeately after creating Customer master

Hi Folks,
Is there a possibility to transfer Customers to GTS immediately after creating Customer master.
I know /SAPSLL/DEBMAS_DISTRIBUTE_R3, but this report should run only at night,
becaus performance...
So the question is, right after creating the customer you can enter a sales order
and in this situation the customer is not in GTS.
We want to transfer the customer automatically right after(or while) creating the customer to GTS.
Is there any way to obtain this?
Thanks
Regards
Dieter

Hello Dieter,
unfortunately it not possible to have it done immediately when you create/change a partner.
These data changes are transferred to GTS via change pointers.
You can schedule the change pointers report every 10 minutes but still it has to be done as bgr. job.
At first Activate Change Pointers for Message Types (BD50)
/SAPSLL/DEBMAS_SLL
and Activate Change Pointers for Reduced Messages - Press create icon to create it. (BD53)
/SAPSLL/DEBMAS_SLL
Then schedule RBDMIDOC for /SAPSLL/DEBMAS_SLL which send changes via IDoc.
Cheers,
Gabriel.

Regarding how to create custom IDOC?

hi experts:
       thank you all in advance for all your answers . .
       I am studying Idoc, Would you please give me an example about how to create custom IDOC , and the basic idea, what's more , give me some material I can refer to . couldn't thank you more
       Best regards
       Frank

Steps To Create Custom IDOC
1.Create Segment Type (WE31)
Go to Transaction code WE31
Enter Segment type, click on Create
Give Description
Enter the Necessary Fields & Data Elements for those Fields.
Save the Changes.
2.Create Idoc Type (WE30)
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
3.Create Message Type (WE81)
Go to transaction code WE81
Change the details from Display mode to Change modenAfter selection, the system will give this message The table is cross-client (see Help for further info). Press EnternClick New Entries to create new Message Type
Fill details
Save it and go back
4.Assign Idoc Type to Message Type (WE82)
Go to transaction code WE82
Change the details from Display mode to Change moden After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
You will get step by step process.
ABAP Development
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
ABAP Development
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
ALE/ IDOC
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
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
i need a sample code regarding to create a custom IDOC...
Reward points...

How to create a simple idoc in practice? can you provide an example?

how to create a simple idoc in practice? can you provide an example with full source code?

Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*</b>

Itegration with Websphere Message Broker and Customer Master IDOC

Hello All. I am new to this forum. I have a couple of questions.
What I am trying to do: I have to interface to SAP with Websphere Message Broker which has inbuilt nodes to interface with SAP using BAPI or ALE to send Customer Master Record (create/update/delete)
The questions I have:
1/ Has anyone done this? What did you use BAPI or ALE?
2/ When a Customer Master IDOC is sent to SAP, if successful, a return code is sent back by SAP. This indicates that SAP has received the IDOC successfully. However, our requirement is that we have to know whether the IDOC was successfully posted within SAP. I am of the opinion that this is manual task within SAP and it should not be the function of the middleware layer as its responsibility is only to successfully deliver the IDOC's. I would welcome opinions on this issue. Please let me know If there is a way to determine if the IDOC has been successfully posted in SAP.
3/ Is there anywhere where I can get an XML representation of the Customer Master Record. I want to see the structure and the available fields. How can I get this info from SAP?
Thank you

Hi;
Similar issue has been answered at -Steven Chan blog*
From blog:
Hello, RM,
I have not seen any Oracle-produced documentation along those lines. I don't think there are any Oracle teams that are investing in producing documentation for IBM WebSphere.
I would suggest contacting IBM to see whether they have produced any WebSphere-specific documentation.
Regards,
Steven
Referance:
http://blogs.oracle.com/stevenChan/entry/ebusiness_suite_release_1211_now_available
Ps: You can rise SR for your issue also
Regard
Helios

How to create custom content placeholder in sharepoint 2013

Hi, I would like to create custom content placeholder don't know how to and add to my custom master page in sharepoint 2013. I have no luck searching on how to create custom content placeholder, any help?
Thanks,
Johnweb

Hi,
If you’re not fixed your requirement with the Out of the box SharePoint place holders, you can create as many as you want as long as the ID doesn’t conflict. On the master page add the content place holder
<asp:ContentPlaceHolderid="CustomName" runat="server"></asp:ContentPlaceHolder> and add this to your page layout
<asp:Contentrunat="server" ContentPlaceHolderID="CustomName"></asp:Content>.
I suggest you provide your basic requirement for further research.
If you want to customize a master page, the Rajendra's method would be helpful.
Best Regards,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Error while creating customer master data

dear sir,
i have created customer master and maintined all level general,compnay code and sales level data.and again deleted all areas thru t-code XD06.and thru se16n i have deleted the entires in kna1 knb1 knvv table
again while creating one with same name showing error while maintaing sales level data
Check: Table KNA1 does not exist, table KNVI does
Message no. F2061
plz help how do i rectify this problem and maintain the same cutomer no (external) again.
regards,
Debesh

Hi,
you did the wrong thing, don't remove the entries from standard table like KNA1, KNVV etc, SAP will maintained the entries in lot of tables same time.
XD06 is used to set delete indicator, after wards you may create new customer master, if any problem for name you may change the name field as 'delete' for old customer.
Now to solve your issue, i believe you need to first save the entries with maintainace of general data (KNA1) and then use XD02 to maintain the Sales area data, pl try this way it should work.
If this way will not work, pl maintain the tax indicator in table KNVI manually to solve the issue.
regards
Vivek.
Edited by: Vievk Vardhan on Dec 7, 2009 6:41 PM

While creating customer master i am getting the Communication error

Hi experts,
while creating customer master i am getting the Communication error with the external tax system (VERTEX_MS0018) please tellme how to solve this issue
Regards,
Anil prasad
Edited by: prasadanil on Sep 16, 2011 12:52 PM

hI Prasad,
It seems you are maintaining the address data for a country with jurisdiction code. Different external control systems can behave in different ways.
1. You entered a jurisdiction code that matches the postal code but not the city (possibly due to a typo).
a) Behavior when you use Taxware: There is no message and data can be saved.
b) Behavior when you use Vertex: Due to the incorrect city, no comparison jurisdiction code can be determined and message TAX_TXJCD861 is issued with a text from the vertex system that may be unintelligible.
2. You do not enter a jurisdiction code, but you do enter a postal code and a city that does not match the code (possibly due to a typo).
a) For Taxware: If the jurisdiction code could not be explicitly determined, a selection dialog box containing the relevant tax jurisdiction codes for the postal code appears. You select one. This and the corresponding city are transferred.
b) For Vertex: The TAX_TXJCD861 message is issued (behavior as in 1b). Other terms TAX_TXJCD861, TAX_TXJCD101, TAX_TXJCD107.
For resolving this issue, you can check SAP Note 677850 - Address data: Check/new determination jurisdiction code.
Hope you will resolve the above issue with these inputs.
Let me know if you need any further details.
Ravi.

Customer master idoc scenario

Hi gurus,
customer master idoc should be sent based on customer group in sales area data of customer data.
for example if customer group is 01 then this customer master data should be sent as idoc and if customer group is 02 then this data should not be sent.
How can this requirment be fulfilled.
Thanks in advance
sameer

>>u can use synch-Asynch bridge using BPM
This can not be done via sync-async bridge.There are 2 reasons for this
1.He has file adapter as sender and that doesn't support synchronous scenarios.
2.He has standard IDOC as receiver.there is no way you can fetch customer# from IDOC without writing a custom program,Thats why i said he need to either use RFC/Proxy or do some custom development.
Thanx
Aamir

How to create customer master IDOC

Similar Messages

Maybe you are looking for