Urgent info : regarding IDOC

hi,
can we post an idoc to a GL(fb02) or any transaction which has been "Batch Enabled"? if yes plz give me procedures how to accomplish this process. if no plz give me the reasons y we can't perform this process.
with regards.
T.Jeyagopi.

Hi,
Are you sure that the fm you found will work?
Because these IDOC fms should normally comply to a standard interface. May be you can create a Z version of IDOC_INPUT_ACC_GL_POSTING and then inside replace BAPI_ACC_GL_POSTING_POST with your fm or something like that.
Any way, I think you can change it in transaction WE57 or in table TBDBE .
If you change it in WE57, go to the entry where Basic Type is ACC_GL_POSTING01 and Message Type is ACC_GL_POSTING, double click on it and change the fm (BAPI_IDOC_INPUT1) to Your fm name.
If you are going to change it in table TBDBE, then you have to find a way to update this table as I could not find Table maintenance for it..
Hope this helps..
Sri

Similar Messages

Regarding IDOC in XI

Dear All,
For scenario:
System A (RFC adapter) --> XI --> System B (IDOC adapter).
How should i configure for the partner profile?
1. In System A --> Logical System to System B, and put my message type as outbound.
2. In System B --> Logical System to System A, and put my message type as inbound.
3. or i need to configure in XI partner profile? Logical system A (outbound) and Logical system B (inbound).
Please clear my doubts.
Thanks,
Victor.

Hey,
   For RFC you do not need to make any entries in partner profile.
For IDOC(i.e) in system B create a partner profile as inbound.
Please refer to these steps if any issues.
teps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
regards,
     Milan

Regarding IDOCS.....

Hii All,
kindly suggest me some links regarding IDOCs, as I need to create one regarding PO.
Points for sure......:)
Regards,
Ashish

Hi
If u want any material giev me ur mail id i'll forward u some documents
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.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
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
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Pavan

How to find out the info regarding Solaris, server hang or shutdown.

Hi
As I am handling the Solaris 9 Server remotely.
As in last week the server has stopped to respond suddenly, we have tried to ping, ssh which was not working. As ultimately we have asked the Data Centre Team to hard reboot the same, to resolve the issue.
In the same ref I would like to know how we come to know the reason, what caused to reboot the same, i.e . any log file, etc..
I have check /var/adm/messages, but not found any detail for the same.
Thanks
Rajan
I

No core files?
No hope for an answer.
As you learned in the other Internet forum.
http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-find-out-the-info-regarding-solaris-server-hang-or-shutdown.-621500/
To get such corefiles analyzed,
you would need to use your service contract and log a support case with Sun.
They have the special software tools to do that.

HT201974 What Key combo is used to see extended info regarding my airport signal?

Can someone tell me the key combinations used to allow me to see extended info regarding my airport signal when I click on airport icon in menubar? things like security key, transmit rate, etc.
I remmeber it being a combination of keys using command button and then left clicking on the aiport icon in the menubar.
Thanks
RezF

Hold down the option key on your Mac while you click on the AirPort icon at the top of the screen.

Very important and urgent - i need info regarding a function module

hi all,
can any one suggest me a function module which calculate the
difference in two dates and give answer in days.
some one suggest me the following function m odule
CALL FUNCTION 'HR_SGPBS_YRS_MTHS_DAYS'
       EXPORTING
            beg_da     = wpv_dati
            end_da     = wpv_datf
       IMPORTING
            no_cal_day = wpv_days
Please suggest any other function module.
or i can use this Function module only

Hi,
U can use the following function module.
CALL FUNCTION 'DAYS_BETWEEN_TWO_DATES'
EXPORTING
    I_DATUM_BIS                   = date1
    I_DATUM_VON                 = date2
I_KZ_EXCL_VON              = '0'
I_KZ_INCL_BIS                 = '0'
I_KZ_ULT_BIS                  = ' '
I_KZ_ULT_VON                = ' '
I_STGMETH                     = '0'
I_SZBMETH                     = '1'
IMPORTING
    E_TAGE                        = days
EXCEPTIONS
DAYS_METHOD_NOT_DEFINED       = 1
OTHERS                        = 2
Reward if useful.
Regards,
Rajesh Akarte

Need info regarding reducing Idocs

Hi,
Iam exteding ORDERS05 to ZORDERS05.
I need to remove segment E1EDS01 from this ZORDERS05.
i tried to reduce using BD53 tcode but it asks for reference message type and throws message saying not available in reduction pool.
pls sugest

ACLs, like Accounts, are optional security setting which may add on some extra functionality to mandatory security groups. Likewise, the resulting permission is taken as an intersection of SG and ACLs.
But in the second part the number of set of users is huge (approx say 600)I don't get this completely. Does this mean that those "sets of users" (users who see the same data) are distinct and that there is 600 of such groups?
If you read thoroughly the manual I sent earlier, there is a recommendation that there should be maximum 50 security groups, and you should use accounts, should this number be exceeded. This means you could have all the documents in one security group (and have one common role with Read permission), but combine it with accounts. ACLs are not a good choice here - their performance and manageability is much worse than of accounts. ACLs are primarily used if you expect security settings to change during the lifetime (e.g. a project manager adds temporarily rights to access an item to another user, and revokes it when the user finishes his or her work).
Note that accounts as well as permissions of users within accounts can also be mapped externally (from LDAP/AD) and it usually follows some kind of org chart.
I'd feel more comfortable not to speak about users, security groups, roles, etc., but about some real-life objects and scenarios.

Very urgent:To find IDOC list in RSMO(BI 7.0)

Hi all,
Its very urgent to know,for a particular load IDOCs used to run to process the data&dialogs,in 3.5 we used to get the IDOCs list in RSMO screen itself,but in 7.0 is not having that options,please tell me for a particular load where we can find list of IDOCs?
Regards,
GTR.

Hi,
This info may be helpful.
Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
Also
Check Note 561880 - Requests hang because IDocs are not processed.
thanks,
JituK

Urgent: Error in idoc(Application document not posted)

Hi experts,
i am getting the error in R/3 side when i am extracting data from it.
i checked with WE07 it's shows the error as follows
"Application document not posted".
it's been urgent how to resolve this issue. please through a light on it.
Regards
Harikrishna N

Hi Hari,
You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
This could be the reason for ur error..
IDoc could not be generated under MC
EDIN: Evaluates the partner data from the MC record
TS70008037
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
this link givs u the req info
[http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
Hope it helps U
Regards,
NR

Regarding idoc to file

hello all,
i am working on a scenario where i need to send an idoc from my r/3 system to xi process it and store it in application layer folder of XI. i am able to see the idoc xml in message monitor also. but i am getting a error message "<SAP:Stack>Party and service not defined</SAP:Stack>" and also i found the following message in trace " <Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000001012 and receiver service</Trace> "
i configured my receiver bussiness system as a third party system with communication channel as file adapter, made also the necessary configuration in both the design and configuration.
where might i have gone wrong, i need some one to help me its really urgent.
thanks,
raju.

hi,
are you using Logical system as Partner profile in R3 to send the idoc ?
if not then:
- either change it to logical system
- configure a party in integration directory for your non LS sender
Regards,
michal

Creation of purchase info using IDOC

We have a requirement where we creating the purchase info (ME11) via IDOC.
Currently we are using basic type "INFREC01" to create Info records.
But this IDOC type has limitations, as this IDOC does not contain scale quantity & some other fields.
To add these fields we have another IDOC type "COND_A04".
So, using this IDOC type to create condition Scale Quantity.
When i am trying to test this basic type COND_A04 in WE19 provding the condition type PB00 and the condition table 017 it gives me error of "Table not available". (checked the condition table in T681 for the condition type pb00)
Can i know how this can be handled?

looks like it accepted A017.
Why did you choose basis type COND_A04 ?
As this one is very special for long material numbers ( more than 18 digit material numbers) do you have such?
E1VFSCAH is the Scale header in case of dimension specific scales. do you have such?
Just try it with COND_A01

Urgent help in IDOC .

helo ,
Please help me in this : How can i get data from the " Characteristics" for my IDOC segment fields ( the characteristics have been created with tcode CT04)..
thanks,

Hi
Use the following BAPI or fun module to fetch the Characteristics and populate the segments
BAPI's:
BAPI_OBJCL_GETDETAIL
or use the fun module:
CLAF_CLASSIFICATION_OF_OBJECTS.
reward points
regards
Anji

Query Regarding IDOC "WMMBID02"

Hi,
I have a follwoing requirement that makes use of a standart IDOC WMMBID02. This IDOC WMMBID02 has data stored within into different segments that have structures. I need to read that data and store it into an INTERNAL Table.
Is there any specific SAP Function Module that would help me to obtain such requirement. If not, what are the options that could be used to read data from IDOC WMMBID02 and populate our INTERNAL Table.
Kindly Suggests,
Thanks & Regards,
Rajesh

Rajesh,
Either you can use the function IDOC_TYPE_COMPLETE_READ
Or use the code as below.
SELECT * from EDID4 into t_idoc_data where docnum = ???
data : wa_E1MBXYH type E1MBXYH,
wa_E1MBXYI type E1MBXYI,
wa_E1MBXYJ type E1MBXYJ
loop at t_idoc_data into wa_idoc_data.
case segnam.
when 'E1MBXYH'.
move wa_idoc_data-data into wa_E1MBXYH.
when 'E1MBXYI'.
move wa_idoc_data-data into wa_E1MBXYI.
when 'E1MBXYJ'.
move wa_idoc_data-data into wa_E1MBXYJ.
endcase.
move corresponding fields of wa_E1MBXYH into wa_itab.
move corresponding fields of wa_E1MBXYI into wa_itab.
move corresponding fields of wa_E1MBXYJ into wa_itab.
append wa_itab to itab.
Clear all the work areas here
endloop.
Regards,
Ravi
Note : Please mark the helpful answers

Help regarding IDOCs

Hi i'm new to SAP..I'm working on developing a new adapter in java called IDOC which converts flat format idoc files (3 idoc object types: Product, Account and SalesOrder) to XML..
We get IDoc files over FTP and these files have to be read from the FileSystem.
I have a few questions here..
1) Do we need to get predefined schemas for Product, Account and SalesOrder idocs ? whether any schemas for these IDOC objects exists ??
2) I have a topical collection of IDoc and segment Definitions.
a) IDOCTYP;NR;SEGTYP;PARSEG;PARPNO;PARFLG;MUSTFL;OCCMIN;OCCMAX;HLEVEL
/DSD/HH_CONTROL01;0001;/DSD/HH_E1CTHD01;;0000;X;X;0000000001;0000000001;01
b) SEGTYP;POS;FIELDNAME;ROLLNAME;EXPLENG;ISOCODE
/DSD/E1BPRACLEARING;0001;VISIT_ID;/DSD/HH_VISIT_ID;0006;
Can anyone please tell me the what these abbravations are (NR, PARSESEG etc..)
Thanks in advance..

parseg means parent segment.......
I think remaining are some of the fields.....
You will have Idoc type,Message type linked with that and all these segments with the fields in it.
All you have to do is configuration in we20....Partner profiles..
regards,
sandeep.

Regarding IDOC 2 FILE Scenario

Hi Friends,
please help on IDOC 2 File Scenario. I have done tha ALE settings in R3 system and the Idoc has been generated out of r3 system. but how it wiil be sent to XI server can any body help me on this issue.make it as quick as possible.

Hi,
Goto We02 and take the IDOC number froom there.
goto WE19, give the copied idoc number and click on execute.
Check for Control records for that IDOC and say outbound processing
ALE Settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Check this for posting the IDOC From R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI+--
StepsSummarized&
Regards
Seshagiri

Urgent info : regarding IDOC

Similar Messages

Maybe you are looking for