Urgent IDOC Error : No description transferred

Hello
I am trying to load an IDOC for Material Master
Using MATMAS 05
Getting a error 51 Application not posted
When check its details it says No description transferred
There is no long text for this error
Your response is greatly appreciated
Thanks

1) You are creating outbound or inbound.
Error 51 is for inbound. Just to make sure.
I think you are doing some abnormal process that's why you didn't see any message.
Thanks,
Narayan

Similar Messages

Urgent: IDOC Error

Hi SDN's,
We are getting error
"system setting does not allow in changing object Idoc XXXXX."
How to resolve it.
It is a bit urgent..
Please help us..
Thanks in advance...
Regards,
Rahul

so what exactly are you trying to change. The content, the structure, or what? The basic Idoc type itself?
If it is an already existing (inbound / outbound) Idoc with actual IDoc number?

BI Load Failure: Error message....IDoc ready to be transferred to applicati

Hello All,
Many loads failed in Production, and in the monitor status it show
Extraction (messages): Missing messages (Status :Yellow)
       Missing message: Request received    (Status :Yellow)
       Missing message: Number of sent records (Status :Yellow)
       Missing message: Selection completed (Status :Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status :Yellow)
       Request IDoc : IDoc ready to be transferred to application (Status :Yellow)
Processing (data packet): No data (Status :Yellow)
I went through the below who has the same issue and solved it by increasing the work process of the IDOC's. Can anybody explain how to increase the work process of the Idocs and also the reason for the failure.
Re: Issue while uploading data from R/3 production to BW production

Hi Ram
I am getting the same error as you have stated here
the error is
Requests (messages): Everything OK (Status:Green)
   Data request arranged (Status:Green)
   Confirmed with: OK (Status:Green)
Extraction (messages): Missing messages
Data request received (Status:Green)
Missing message:No of sent records (Status:Yellow)
Missing message:Selection completed (Status:Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status:Green)
Request IDoc : IDoc ready to be transferred to application (Status:Green)
Info IDoc 1 : Application document posted (Status:Green)
Processing (data packet): No data
Please...... I think you cn guide me in this as u already resolved this type of error
Thanks in advance

Error - Conditions in IDoc E1EDP05 have been transferred: Check data

Hi
I am procesing a ORDERS05 idoc .
in foreground the document is posted but when i run the idoc in background i get the following error.
<b>Conditions in IDoc E1EDP05 have been transferred: Check data
</b>
any idea why is such an error is occuring
Thanks
Nikhil

Hi,
I have same problem here 'Conditions in IDoc E1EDP05 have been transferred: Check data' while transfer PO to SO.
I have tried in doing SMME, but it show me 'Client 800 has status 'not modifiable''.
What I should do the next?
Many Thanks.

Urgent IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

Hi,
Please refer to this documentation of user-exit; may be of some help for you.
You can use this user exit to influence the processing of IDOCs of the
message type WMMBXY (goods movements) that are sent to SAP from external
systems via the MM-MOB or WM-LSR interfaces. You can also access
customer-specific processing in this case.
Call transaction and other important requirements
The user exit is performed in the function module that processes the
IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
checked but before direct processing in the application has been
initiated. (That is, the data for the goods movement has already been
determined and edited, but the function module for updating this has not
yet been accessed. The standard function module for processing the
message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
in an update task, which means that the source code is also executed in
the update.
If an error arises, then messages should not be issued since processing
is being carried out in the background and the result of processing must
always be returned to the ALE interface. For this reason language
elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
used. If errors that should be passed on to the ALE interface or that
affect the result of processing are found in the user exit, you should
also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
used to take your errors into account (see documentation of the user
exit).
Parameters and options
The user exit in the program is the function module EXIT_SAPLLMDE_002.
In order to be able to use it, you must first create Include zxlidu10
and activate the enhancement by means of transaction CMOD. As
parameters, you can use the following data:
o   Goods movement data already determined from the received IDOC:
    -   Transaction code that is given along with the application
        function module (see interface description (import parameter
        X_TCODE).
    -   Indicator: post only if all items o.k. (import parameter X_XALLP
        ). This indicator must be set by default, to enable IDOC error
        processing.
    -   Indicator: Reset all tables (as primary call) (import parameter
        X_XALLR). This indicator is not set by default to enable the
        processing of several IDOCs. Normally you will not change these
        two indicators.
        -   Goods movement items table (table parameter T_IMSEG)
    o   Received IDOC data:
        -   IDOC control record (import parameter I_IDOC_CONTROL)
        -   IDOC data records (table parameter T_IDOC_DATA)
    This user exit can be used to:
    o   Influence the determined data for the goods movements. All data can
        be changed in this case.
    o   Analyze and process data that is transferred using customer-specific
        segments.
    o   Access additional activities.
    Examples
    A number of potential applications are described below.
A number of potential applications are described below.
o   You want to inform a user by mail when the goods movements of
     certain vendors or customers take place.
o   You want to start your own label printout, for example at goods
     receipt.
o   You want to update your own tables, for example statistical data.
o   You want to analyze a missing parts table at goods receipt and
     redirect the goods receipt correspondingly.
Reward points if helpful.
Regards,
Pankaj Sharma

Terms of payment in IDoc E1EDK18 have been transferred: Check data

hi Firends,
In my scenario , i have to convert incoming purchase order to sales order in my system . I am able to get message from partner and idoc is created to the message bt it contains error,
tht is Terms of payment in IDoc E1EDK18 have been transferred: Check data
related to this I had gone through note 388120 - Transfer of conditions and terms of payment.
which says that i have to maintain tht entry in SMME tcode.
My confusion here is, while I tested same scenario in development , and quality server , it was not giving any such error bt in prod system i m gettin this error.
Also if some one knows more details abt this note ,let me know.
Thanks ,
Brijesh Soni

Hi Brijesh,
you are more likely to get a response for this query if you create a thread in the SD forum.
Regards
Kenny Scott
XI/PI SDN Forum Moderator

IDOC to IDOC Error

Hi ,
I am doing an IDOC to IDOC scenario. Idoc from source system is successfully sent to xi and xi is able to delivery the idoc to the target system. When the idoc is posted to target system the status is 64 IDoc ready to be transferred to application. When I run the RBDAPP01 report it is giving me dump. Find below the dump
Can any one throw some light on it please?
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          28.09.2007 09:28:27
     Short text
          Field symbol has not yet been assigned.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "SAPLHRALX00_INTEGRATION_PERSON" had to be terminated
           because it has
          come across a statement that unfortunately cannot be executed.
     Error analysis
          You attempted to access an unassigned field symbol
          (data segment 32785).
          This error may occur if
          - You address a typed field symbol before it has been set with
            ASSIGN
          - You address a field symbol that pointed to the line of an
            internal table that was deleted
          - You address a field symbol that was previously reset using
            UNASSIGN or that pointed to a local field that no
            longer exists
          - You address a global function interface, although the
            respective function module is not active - that is, is
            not in the list of active calls. The list of active calls
            can be taken from this short dump.
     Trigger Location of Runtime Error
         Program     SAPLHRALX00_INTEGRATION_PERSON
         Include     LHRALX00_INTEGRATION_PERSONF52
         Row     486
         Module type     (FORM)
         Module Name     IDOC_CONVERT
     Source Code Extract
     Line     SourceCde
       456                 add_idoc_msg ct_idoc_errors <ls_segment>-docnum <ls_segment>-segnum gc_idoc_warn
       457                              'RH_ALEOX_INTG_CP_IDOC_1' 'IDOC_CONVERT/MAPPING'.
       458                 CLEAR <ls_segment>-segnam.
       459                 CONTINUE.
       460               ENDIF. "mapping
       461
       462             ELSEIF <ls_e1pad31>-sclas = gc_quali AND
       463                    <ls_e1pad31>-otype = gc_pernr AND
       464                    <ls_e1pad31>-relat = gc_q_cp_subty+1.
       465
       466               <ls_e1pad31>-otype = gc_cpers.
       467               <ls_e1pad31>-objid = <ls_mapping>-objid.
       468
       469               PERFORM idoc_convert_1001_q USING   <ls_segment>
       470                                           CHANGING et_e1p1001_q
       471                                                    et_refobj_q.
       472               PERFORM idoc_convert_5586 CHANGING <ls_segment>.
       473
       474             ENDIF.
       475     *     -
       476           WHEN gc_e1p0000.
       477     *     -
       478             PERFORM idoc_convert_pa_infty USING    gc_cpers
       479                                                    <ls_mapping>-objid
       480                                                    '5580'
       481                                                    space
       482                                                    <ls_mapping>-begda
       483                                                    'E1P5580'
       484                                           CHANGING <ls_segment>.
       485     *     -
     >>>>>           WHEN gc_e1p0001.
       487     *     -
       488             APPEND <ls_segment>-sdata TO lt_segment_0001.
       489             PERFORM idoc_convert_pa_infty USING    gc_cpers
       490                                                    <ls_mapping>-objid
       491                                                    '5581'
       492                                                    space
       493                                                    <ls_mapping>-begda
       494                                                    'E1P5581'
       495                                           CHANGING <ls_segment>.
       496     *     -
       497           WHEN gc_e1p0002.
       498     *     -
       499             APPEND <ls_segment> TO lt_segment_0002.
       500             PERFORM idoc_convert_pa_infty USING    gc_cpers
       501                                                    <ls_mapping>-objid
       502                                                    '5582'
       503                                                    space
       504                                                    <ls_mapping>-begda
       505                                                    'E1P5582'
Thanks
Mohammad

Hi Mohammad
you should post in the ABAP forum, there is a quick, good answer expectable.
Regards,
Udo

IDOCs error in Production System

Hi Gurus,
In Production system, there is a CRM oppertunities process chain is running on hourly basis, the data was updated to DSO successfully, but for the past one week it was not updating to further processing InfoCube, there is an error.
error: Idoc Ready to be transferred to application.
Please update me step by step procedure.
Thanks

Hi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks
Reddy

Request Idoc : Idoc ready to be transferred to application

Hi
I am getting the above error.
I am not able to process further.
In the details tab i am getting the following errors.
1 Extraction:missing messages
2.Transfer(Idoc and tRfc):ERRORS Occured
Request Idoc : Idoc ready to be transferred to application.
3. Processing : no data
4 Process Chains: Error Occured.
All of these errors are in Red.
I have cheked in BD87 WITHTHE IDOC NO. IT shows red status with Idoc enteries in tRFC queues
I don't know how to proceed further.
Please help in this issue asap.
Thanks in advance.

1) 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
This should help.
Also check these transactions to get more info on IDOCS.
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDoc in Database
WE10 Search for IDoc in Archive
WE23 Verification of IDoc processing
Thanks,
JituK

Missing IDoc and recurring IDoc errors

Hi,
I would like to ask for a help or any ideas on below case.
We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and description "EDI: IDoc 63120 does not exist, please check data".
This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
Your response will be helpful in solving my problem.
Thanks in advance!

Hi Juan Francisco Zurita Duque
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
Use
Sold-to party number sent in by the customer in delivery schedules.
Use
The system uses this number to automatically determine the ship-to party.
Every thing good for ORDRE05 IN ECC6.0
Check your config settign related to Message type and idoc type.....once again.....
RR

Idoc error- Balance in transaction currency

Dear Experts,
In we02, I found idoc error with the following messages:
Balance in transaction currency
Message no. F5 702
Diagnosis
A balance has occurred in transaction currency 'XXX' with the following details:
Exchange rate '00', amount ' 1.413.696' and currency key 'XXX'.
The data in the transaction currency were transferred from the calling application.
System Response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.
Please advice, how to correct this problem.
Thank you in advance.

Hi Natasha,
Please check the "EDID4" table to find the error why it is not allowing to post.
Also check "WE09" to check the status of the IDOC.
You can process it manually through "BD87"
Bye
Swapna murali

Interface idoc error

hai sapians,
when iam trying to post the sales order docu using inbound idoc this is wat iam getting in status of idoc
status 51:control data in idoc EIEDK04 has been transferred.check data
anybody help me to resolve it.
thank u.

Hi,
Go to WE19 .In the main screen give the error idoc number and execute.Now in the second screen in the inbound function module tab in appication tool bar give the FM IDOC_INPUT_ORDERS and then select the check box CALL IN BEDUG MODE and press the radiobutton IN FOREGROUND.Now debug the FM and see whre that error is coming and rectify the same..
plz award points if u find useful.
Regards,
Nagaraj

Sales order idoc error only on ORDCHG message type (ORDERS01)

Hi. I am adding segment E1EDK04 to our sales order idocs in order to pass tax jurisdiction code to R3. When I create the order (message type ORDERS), I am extracting tax jurisdiction code from the idoc and I am adding it to the ship-to address screen via a BDC table within user exit include zxvedu04. The new order gets saved with the TXJCD, and this works fine.
I am now testing maintenance scenarios. For ORDCHG message types, I am inserting the TXJCD within user exit include ZXVDBU02. The idoc processor abends in 51 status with message:
"Control data in the IDoc E1EDK04 has been transferred. Check data".
If I walk the same status 51 idoc through BALE without changing anything, I see the TXJCD get posted to the order, and the order is saved correctly the second time.
Does this mean I need to add something additional to the idoc control data on an ORDCHG or something?
Thank you.
Brendan

I was not able to get any farther on this. It would seem that when the idoc is processed in the foreground, something is being populated that is not present when the idoc come across to R3...
The thing is, when I walk through the idoc in the forground, there are no errors that pop up. I can save the idoc after foreground processing and it moves into 53 status.
Thanks for any ideas that you might have on how to gather more infromation.

IDOC Error Report

Dear All,
There is an requirement to generate IDOC error report.
Normally t.codes we02 / we05 are used to see the idoc errors. I would like to know whether any transparent tables are available to see the error log.
More specially, I need to generate an report with IDOC Numer + Error Description as an output.
If any clues, please pass on the same.
Regards,
Ramki.

Hi Ramki ,
Below is the code to read the error messages also for Inbound IDOC , For Out bound you have to relay on the EDIDS record only ......
Inbound : Application Log will have detailed messages for each and every error.
TABLES : edidc.
TYPES : BEGIN OF ty_final ,
        docnum      TYPE edidc-docnum,
        status      TYPE edidc-status,
        direct      TYPE edidc-direct,
        rcvprn      TYPE edidc-rcvprn,
        sndprn      TYPE edidc-sndprn,
        credat      TYPE edidc-credat,
        last_run    TYPE edids-credat,
        cretim      TYPE edidc-cretim,
        mestyp      TYPE edidc-mestyp,
        message     TYPE char255,
        END OF ty_final.
DATA : lt_final    TYPE TABLE OF ty_final,
       ls_final    TYPE          ty_final,
       lt_messages TYPE STANDARD TABLE OF balm,
       ls_messages TYPE                   balm.
SELECT * FROM edidc INTO TABLE lt_edidc
          WHERE       upddat BETWEEN lv_date AND sy-datum
          AND         status IN s_staus
          AND         direct = c_2
          AND         mestyp IN s_mestyp
          AND         credat BETWEEN lv_date AND sy-datum
          AND         cretim BETWEEN lv_ltime AND sy-uzeit
          AND         rcvpor = lv_rcvpor
          AND         rcvprt = lv_rcvprt
          AND         rcvprn = lv_rcvprn
          AND         sndpor = lv_sndpor
          AND         sndprt = lv_sndprt
          AND         sndprn = lv_sndprn
          ORDER BY PRIMARY KEY.             " select the failed Idocs
SORT lt_edidc BY docnum ASCENDING.
IF NOT lt_edidc IS INITIAL.
    SELECT * FROM edids INTO TABLE lt_edids FOR ALL ENTRIES IN lt_edidc
                                            WHERE docnum = lt_edidc-docnum.
    SORT lt_edids BY docnum ASCENDING countr DESCENDING.
    TRY.                                                    "#EC NEEDED
      CATCH cx_sy_dyn_table_ill_comp_val.               "#EC NO_HANDLER
    ENDTRY.
    DELETE ADJACENT DUPLICATES FROM lt_edids COMPARING docnum.
    LOOP AT lt_edids INTO ls_edids.
      lv_extnum = ls_edids-docnum.
      CALL FUNCTION 'APPL_LOG_READ_DB'         " To get Application Log details for Each Idoc
        EXPORTING
          object           = '*'
          subobject        = '*'
          external_number = lv_extnum
          date_to          = sy-datum
          time_from        = '000000'
          time_to          = sy-uzeit
          log_class        = '4'
          program_name     = '*'
          transaction_code = '*'
          user_id          = ' '
          mode             = '+'
          put_into_memory = ' '
        TABLES
          messages         = lt_messages.
      DELETE lt_messages WHERE lognumber NE ls_edids-appl_log. " Delete Messeages where APPl_log NE latest
      DELETE lt_messages WHERE msgty NE 'E'. " delete other than Error messages
      LOOP AT lt_messages INTO ls_messages.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id   = ls_messages-msgid
            lang = 'EN'
            no   = ls_messages-msgno
            v1   = ls_messages-msgv1
            v2   = ls_messages-msgv2
            v3   = ls_messages-msgv3
            v4   = ls_messages-msgv4
          IMPORTING
            msg = l_msg.               " Actual Error Message received
        ls_final-docnum    = ls_edids-docnum.
        ls_final-status    = ls_edids-status.
        ls_final-last_run = ls_edids-credat.
        ls_final-cretim    = ls_edids-cretim.
        ls_final-message   = l_msg.
        CLEAR : ls_edidc.
        READ TABLE lt_edidc INTO ls_edidc WITH KEY docnum = ls_edids-docnum.
        IF sy-subrc = 0.
          ls_final-credat = ls_edidc-credat.
          ls_final-direct = ls_edidc-direct.
          ls_final-rcvprn = ls_edidc-rcvprn.
          ls_final-sndprn = ls_edidc-sndprn.
          ls_final-mestyp = ls_edidc-mestyp.
        ENDIF.
        APPEND ls_final TO lt_final.       " Final Table will have Failed Idocs with Error Messages
        CLEAR ls_final.
      ENDLOOP.
      IF lt_messages IS INITIAL.
        CLEAR ls_final.
        ls_final-docnum    = ls_edids-docnum.
        ls_final-status    = ls_edids-status.
        ls_final-last_run = ls_edids-credat.
        ls_final-cretim    = ls_edids-cretim.
        CLEAR : l_msg.
        CONCATENATE ls_edids-stapa1 ls_edids-stapa2 ls_edids-stapa3 ls_edids-stapa4 INTO l_msg SEPARATED BY space.
        CONDENSE l_msg .
        ls_final-message   = l_msg.
        CLEAR : ls_edidc.
        READ TABLE lt_edidc INTO ls_edidc WITH KEY docnum = ls_edids-docnum.
        IF sy-subrc = 0.
          ls_final-credat = ls_edidc-credat.
          ls_final-direct = ls_edidc-direct.
          ls_final-rcvprn = ls_edidc-rcvprn.
          ls_final-sndprn = ls_edidc-sndprn.
          ls_final-mestyp = ls_edidc-mestyp.
        ENDIF.
        APPEND ls_final TO lt_final.
      ENDIF.
    ENDLOOP.
ENDIF.
Final Table will now have all the error reasons for each and every Idoc ....
Hope this will help your requirement

Hi Ragarding....Idocs Errors, ODS Functionality

Hi Gurus
Pls Urgent
Can U explain the --> Idoc Errors....and how to solve
                          ---> Ods( Whether functionality...Addition / Subtraction)
                          ---> Ticket Procedure and how do maitain this
                          ---> how many views can be created in generic Extraction
pls do the needful
regds
Pandu

HI,
ODS : has overrite functioanlity where info cube has additive fucntioanlity.
So, every time we shud recommend ODS in between datasource and Infocube.
Another imp point is , if the datasource is not supporting delta fucntionality, how do we handle the situation? right.
So use ODS, from the datasource load the data till ODS and as ODS contains changelog with 0recordmode with before and after images, we can perform the delta functinality to the Cube.
Ticket procedure:
See, we have third party ticketing tools like Gremedy, clarify, lotus notes etc.
Ticket means- defect or issue in the data or application or technical object.
So user raises the ticket and it wil assigned to concerned technical resource by the helpdesk and based on the priority of the issue, technical peopel should resolve the issue or ticket with in the SLA(Service level aggrerment).
Views : View is nothing but a image of the tables.
So we can call up multiple tables in a view for generic extraction.
Hope this info helps.
Thanks,Ramoji.

Urgent IDOC Error : No description transferred

Similar Messages

Maybe you are looking for