Populating the SEGMENT attribute for IDocs

When mapping to an IDoc, each IDoc data element has a corresponding SEGMENT attribute, which I assume is the sequential segment number of the segment in the IDoc.
Does that value need to be set, or does the IDoc adapter take care of it? If I do need to map it, how can I do it, because I would need to find a way of generating a running number either in the mapper, or externally in an XSL mapping file.

Hi,
OK thanks for explicitly stating thae answer! I was hoping for that.
BR,
Tony.

Similar Messages

TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC

Hello,
Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
Did someone experience this issue ? How did you handle it ?
Regards.
Eric.

Dear Eric
The latest pack available now for these components are (for PI 7.1)
SAP BASIS 7.11 support package 6
SAP HR 6.04 with Support Package 44
If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
Sourabh

How to deactivate the marketting attributes for BP in CRM

Hi,
how to deactivate the marketting attributes for BP in CRM
I can add and maintain the same using tcode crmd_prof_char
But how do I deactivate.
Points will be rewarded
Thanks

.

An error occured while creating the original attribute for message no26 296

Hi All,
I am new to DMS , we are trying to store PM documents on content server , created a storage category and while assigning files to storage category then on saving the document i get the below error :
An error occured while creating the original attribute for
Message no. 26 296
Diagnosis
An error occured while creating an original in the Knowledge Provider.
System Response
The original could not be created.
Procedure
Contact the systems administrator and check the log file (transaction Evaluate application log, object SDOK).
Please let me know what configs i am missing ...
Thanks in advance
regrds
pushpa

Hi Pushpa,
Which enhancement package are you on currently? This is observed in cases where originals in DIR's are invisible and sometimes error message 26296 occurs in transaction CV01n. Hence,please check your entries in the table SDOKPROP to avoid such a problem in your system.
Further,suggest you explore if the below resolutions can be adopted in your case.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=10321987
http://wiki.sdn.sap.com/wiki/display/PLM/OriginalsinvisibleafterEHP3or+EHP4
Regards,
Pradeepkumar haragoldavar

Jdev11G XMLMenuModel : Setting the "destination" attribute for the itemNode

Hi,
I am trying to set the "destination" attribute for the itemNode in the metadata.xml.This is the URI to which the user must be taken on clicking that node. But it is unable to pick the URI set for the destination attribute and hence there is no navigation that happens.Using the "action" attribute works fine. But I need to use the "destination" attribute.
Here are some of the files:
The metadata.xml (root_menu.xml):
<?xml version="1.0" encoding="windows-1252" ?>
<menu xmlns="http://myfaces.apache.org/trinidad/menu">
<groupNode id="groupNode1" idref="itemNode1" label="Merchant">
<itemNode id="itemNode1" label="Sites" action="site_action" rendered="#{testBean.test}"
focusViewId="/common/site/Site.jspx">
</itemNode>
<groupNode id="groupNode2" idref="itemNode2" label="Settings">
<itemNode id="itemNode2" label="Page Template" action="template_action"
focusViewId="/common/template/TemplateRules.jspx">
</itemNode>
<itemNode id="itemNode3" label="Configuration Parameters" destination="http://www.google.com"
action="config_action" focusViewId="/common/others/ConfigurationParameters.jspx">
</itemNode>
</groupNode>
<groupNode id="groupNode3" idref="itemNode4" label="System Admin">
<itemNode id="itemNode4" label="Cache Invalidation" destination="/faces/common/others/CacheInvalidation.jspx"
focusViewId="/common/others/CacheInvalidation.jspx">
</itemNode>
</groupNode>
</groupNode>
</menu>
The faces_config.xml:
<?xml version="1.0" encoding="windows-1252"?>
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
</application>
<navigation-rule>
<navigation-case>
<from-outcome>site_action</from-outcome>
<to-view-id>/common/site/Site.jspx</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>template_action</from-outcome>
<to-view-id>/common/template/TemplateRules.jspx</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>config_action</from-outcome>
<to-view-id>/common/others/ConfigurationParameters.jspx</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>cache_action</from-outcome>
<to-view-id>/common/others/CacheInvalidation.jspx</to-view-id>
</navigation-case>
</navigation-rule>
<managed-bean>
<managed-bean-name>root_menu</managed-bean-name>
<managed-bean-class>org.apache.myfaces.trinidad.model.XMLMenuModel</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>createHiddenNodes</property-name>
<value>false</value>
</managed-property>
<managed-property>
<property-name>source</property-name>
<property-class>java.lang.String</property-class>
<value>/WEB-INF/root_menu.xml</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>testBean</managed-bean-name>
<managed-bean-class>testBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
</faces-config>
Can you please tell me what else has to be set for the "destination" attribute to work?
Thanks,
Swapna

The code you sent is not clear, could you send your jspx page.
Thanks

An error occured while creating the original attribute for

Hi All,
We encounter this error in "An error occured while creating the original attribute for " DMS very often when a user edits a file & tries to check in.
I searched the forums & realized that this is caused by the inconsistencies in the KPRO & DMS server and removing these
inconsistencies will repair this issue.
I have been deleting the inconsistencies using DMS reports DMS_KPRO_READ & DMS_KPRO_CHECK1 and it resolves the error
so the file is unlocked. But I haven't been able to figure out the ROOT cause of this issue.I couldn't find any information on the root cause of this issue. What can be done to fix this error permanently.
Regards
-Neha

Hi Neha,
Please go to transaction SE16 and enter 'SDOKPROP' as table. Then enter 'DMS*' in the field PROP_NAME and press F8. Now all DMS related entries should be displayed to you. Please compare them with the following entries displayed in the attached screenshot and maintain the missing entries.
DMS_ACTIVE_VERSION 00 Active Version
DMS_APPLICATION 00 Logical application
DMS_CHECKOUT_USER 00 Checkout User
DMS_CREATE_AUDIT 00 Generate new version of the original
DMS_DEFAULT_LANGUAGE 00 Default Language
DMS_DELETEABLE 00 PHIO deletable
DMS_DOC_KEY 02 IWB_DMS01 DMS_DOCKEY Document info record
DMS_DOC_VERSION 00 Version of relevant document
DMS_DRAW_APPNR 00 Application number from DRAW
DMS_DRAW_DTTRG 00 Data carrier from DRAW
DMS_DRAW_FILEP 00 File name from DRAW
DMS_FILE1 00 File name(firstpart)
DMS_FILE2 00 File name(secondpart)
DMS_FILE3 00 File name(thirdpart)
DMS_FILE_ID 00 GUID that points to table DMS_PHIO2FILE
DMS_FRMTXT 00 Format description, ID of additional file
DMS_MUP_CAT 00 Markup category
DMS_MUP_FLAG 00 Markup flag
DMS_ORDER 00 Sequence of additional files
DMS_STATUS 00 Document status
DMS_STATUSNR 00 Number in status protocol
DMS_STATUSNR_X 00 References to Status Log
Please pay attention that all entries are typed well and that there are no spelling errors. If all these values are maintained correctly in table SDOKPROP the dump and the error message should no longer appear.
For further information you can also see the corresponding SDN WIKI page under
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/plm/error26296in+CV01N
Regards,
Ravindra

Populating the segments of idocs

Hi,
How do segments of the idoc get populated with data from SAP tables ? (for SAP standard idoc or newly created idoc and outbound process)
Can anyone say in details?
Good answer will be rewarded
Thanks ,
Manas Behera

For any IDOC there is a specific standard function module assigned that is called to fill the IDOC segments.
For orders it is e.g. IDOC_OUTPUT_ORDERS.
This function takes care of the filling of the IDOC segments. You also usually have user exits available in those function modules that you can use to manipulate the IDOC data or fill/add custom segments/fields.
The function modules usually start with IDOC_OUTPUT_* for outgoing IDOCS and IDOC_INPUT_* for incoming IDOCS.
Hope that helps,
Michael

Has anyone populated the doc_flow details for an ORDERS05 IDOC?

I am having trouble understanding what needs to be populated in the doc_flow itab of line type CRMXIF_DOC_FLOW_I.
In my case I am trying to populate the doc flow with CONSIP (customer reference contract) details. I can work out what field 'RELATION_TYPE' is and can see that it needs to have a value of 'VONA'. This one is easy to identify because of the 4 character field definition, but I can't work out what goes in the relobj_roletype, relobj_objkey, relobj_type, or the relobj_object_id fields. Can anyone be of help here. I have been trying a number of different values, for example, I populated the relobj_roletype field with 'BUS2000135' which is the object name for a 'CRM Customer contract', but that was rejected and resulted in a status 51 being set in the IDOC.
Blue

Stephen,
I agree with you, but you try and get a VAN to supply IDOC related details in the complex data structure format. They can do it but they're not at all happy about it and go to great lengths to avoid, whereas the ORDERS05 is a standard that most already output to.
I can process ORDERS05 type IDOC's okay, although I had to add my own code to process a few segments. Anyway, the orders are being created okay. I did initially have a problem when blocking an item, based on certain checks perfromed in the BADI, but that has now been resolved. My only other problem, which a support message has been raised with SAP about, is to parse back status messages to IDOC. Again, there's a BADI which allows you to add content, but there's a mismatch in parameters between the FM and BADI. I'm sure they'll sort it out.
The only thing left now is to get the item level doc flow to update when pointing to customer reference contract. Again, it's just a case of reverse engineering the data from the IDOC created by the CRMXIF_ORDER_TEST program.
Regards
Dr Sidewalk

Ship to party not populating in segment in whsord idoc

HI,
we are creating two delivery with ship to party as 52004 and 56003 (two different sales orders with differnt sold to ). the deliveries are trigerring outbound whsord idoc. The issue is in the segment E1ADRM1 segment for WE qualifier , in the field, " Partner_id", the ship to party 52004 and 56003 is not populated. Rather a constant value 32500000789 is populated in "partner_id " field in both deliveries
Our Abaper is not willing to identiy the same since it is s standard idoc.
Pls can you help as to w hy ship to 52004 and 56003 is missing in partner_id field and some other value 32500000789 is coming ? all other deliveries are created ok.
rgds
Pamela

Hi Pamela,
can you Please share some more information like IDoc details. so that v can analyze more.
Regards,
VSN

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
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
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
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
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
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
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

To add field in the segment of an IDOC

Hi,
Is there any impact on other IDOC types, if a field is added in the segment of an basic IDOC type.

Hi,
You can add the field VGBEL in the custom segment ZE1EDL24 and add this segment as a child segment to E1EDL24 and save it as an extension for the basic idoc type.
You can populate the VGBEL field using custom code in the function exit.
This would solve your problem.
Please let me know if you have any further queries.
Thanks,
Mahesh,

Problem in populating the delivery text in Idoc

Hi Experts,
       We are using a custom EDI output type for VT02n transaction. Currently we are encountering a problem when we set the dispatch time as 'Send immediately'.
       The problem is some of the characters in delivery texts are missing in the segment of the idoc generated.
       The problem does not occur when we set the dispatch time as 'send with application own transaction'.
       But we did not do any coding based on the dispatch time.
       Please provide us suggestions to solve this problem.
Regards
K Arasu.

Hi,
Check whether you have maintained the condition records for output for the above combination & also the Print device in the Communication tab & Print immediately settings.
If you haven't maintained the above, do the same & check.
Thanks & Regards,

Change segment name for Idoc created through BDBG transaction

hi all,
I have created a BO thru SWO1 transaction and then have used BDBG. Now for one of the segments in the IDoC which got generated automatically,i would like to change the segment name.This object was completed long time back and hence was released. Now we have been asked to get the segment name changed. But, when i try to click on the change button it says "<b>the object has been generated and hence cannot be changed"</b> Is there an work around for this? Pls reply. Thanx
Regards,
Venkat

Hi,
I have the same error. Did you solve it?
Regards,
Lyda

How does sap do the material determination for IDOC/EDI?

how SAP do the material determination for inbound PO?
If customer send in their material# or UPC code or buyer material#, what is the order of material determination?
PO1*7CA**UN005650060211VN41112IN515734µ

Hi Samuel,
If the customer sends in their material number this need to be mapped with the value '001' to the field E1EDP19-QUALF and the material number mapped with E1EDP19-IDTNR.
This value is referenced with the CMIR ( Customer material info record) and the vendor's material number is determined which would be used to create the sales order from the inbound PO.
As Such the order of the material determination is depends upon the order it appears in the IDOC.That means the mapping done at the EDI subsystem determines the order of the E1EDP19 segments.
Common practice in EDI inbound P.O scenario,customers send their material number and the vendor material number is determined from the KNMT table.To find the unique material number we need to supply the sales area details as well.
I hope this is answered your question.
Feel free to get back to me if you have any questions.
Thank you.
Regards,
Karun.M

Setting the logonHours attribute for a user in Active Directory

Hi Anyone,
I'm a brasilian guy and I need your help. How can I set the logonHours attribute on my Active Directory?
I have this code but it doesn't works good:
    public void setLogonHours(boolean[] logonHoursBits){
        int i;
        int j;
        int k;
        int index21 = 0;
        int index24 = 0;
        byte[] byteLogonHour = new byte[21];
        byte byte8Hours = 0;
        for(i=0; i <= 6; i++){
            for(j=1; j <= 3; j++){
                for(k=7; k >= 0; k--){
                    if (i < 6){
                        if (logonHoursBits[i] == (boolean)(index24 == 0) ? true : false){
                            byte8Hours += (byte)Math.pow(2,k);
                    else{
                        if (logonHoursBits[0] == (boolean)(index24 == 0) ? true : false){
                            byte8Hours += (byte)Math.pow(2,k);
                    index24++;
                byteLogonHour[index21] = byte8Hours;
                index21++;
            index24 = 0;
        try{
            String nome = "CN=Dryelle,OU=Pesquisa,DC=cifya,DC=com,DC=br";
            ctx = new InitialLdapContext(env,null);
            ModificationItem logonHours[] = new ModificationItem[1];
            logonHours[0]= new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("logonHours",byteLogonHour));
            ctx.modifyAttributes(name,logonHours);
            System.out.println("Atributo logonHours alterado com sucesso.");
        catch (NamingException e) {
           System.err.println("Problema na altera??o " + e);
    }the code set the attribute but wrong. Can anyone help-me? It's making me crazy.
Sorry about my poor english.
Tks.
Edited by: th_slopes on Aug 15, 2008 5:50 PM

DirContext ctx = new InitialDirContext(pr);
          BasicAttributes entry = new BasicAttributes(true);
          String entryDN = "cn=CharbelHad,ou=test users,dc=test,dc=dev";
          Attribute cn = new BasicAttribute("cn", "ChHad");
          Attribute street = (new BasicAttribute("streetAddress", "Ach"));
          Attribute loginPreW2k = (new BasicAttribute("sAMAccountName", "[email protected]"));
          Attribute login = (new BasicAttribute("userPrincipalName", "[email protected]"));
          Attribute sn = (new BasicAttribute("sn", "Chl"));
          Attribute pwd = new BasicAttribute("unicodePwd", "\"Ch@341\"".getBytes("UTF-8"));
Attribute userAccountControl = new BasicAttribute("userAccountControl", "512");
          Attribute oc = new BasicAttribute("objectClass");
          oc.add("top");
          oc.add("person");
          oc.add("organizationalPerson");
          oc.add("user");
          // build the entry
          entry.put(cn);
          entry.put(street);
          entry.put(sn);
          entry.put(userAccountControl);
          entry.put(pwd);
          entry.put(login);
          entry.put(loginPreW2k);
          entry.put(oc);
          ctx.createSubcontext(entryDN, entry);

Populating the SEGMENT attribute for IDocs

Similar Messages

Maybe you are looking for