Data Inconsistent at Standard Structure IS_BIL_INVOICE-IT_GEN

Dear Experts,
I am working on an invoice,data is inconsistent at standard structure is_bil_invoice-it_gen.
I have 26 line items in one invoice but standard structure displays 38 line items. Also i checked standard
structure at the entry of my form by placing a break-point.I would like to know how data flows to this standard structure ? ,I am not doing anything in my form to move data in to this structure.So please
provide me a solution to this problem.
Regards,
Sujay.

HI ,
I dont think you can control the data coming into the standard structure in any possible way . what i would suggest is copy this driver program to your own z program and use this structure to get the header values and texts . for the item level detail you can very well write your own code inside the smart form as the key fields are provided at the header level.

Similar Messages

IDOC data inconsistency

Hi experts,
i have an issue that there is data inconsistency in IDOC( delivery address created with respect to PLANT instead of STORAGE LOCATION).
now i want to rectify the issue by checking the mapping in the program , the IDOC is created by standard procude ( thorough ME21N).
can anybody tell me how can i find the program/interface name where the logic is written for filed mapping for IDOC
IDOC type ORDERS05
Message type ORDERS
Thanks
Niru

Hi ,
I have put a breakpoint inside the FM IDOC_OUTPUT_ORDERS and try to reprocess the idoc from WE19, but the control not stoped at Break point .
assume below is validation inside the FM makng the issue.
IF pekko-werks NE space AND
      pekko-kunnr EQ space AND
      pekko-emlif EQ space AND
      pekko-adrn2 EQ space AND
      pekko-adrnr EQ space.
     CLEAR int_edidd.
     CLEAR e1edka1.
     int_edidd-segnam = 'E1EDKA1'.
     e1edka1-parvw = 'WE'.
*- if Third party order, send customer number of first S.O. item -----*
     PERFORM fill_kunnr_header.
     e1edka1-lifnr = pekko-werks.
     lv_prog = 'SAPLEINM'.
     PERFORM fill_e1edka1_we_gln IN PROGRAM (lv_prog) IF FOUND.
     PERFORM edka1_fuellen.
* Call Method PROCESS_IDOC_SEGMENT (BADI MM_EDI_ORDERS_OUT)
     PERFORM badi_process_idoc_segment.
* Call Customer Function 002 (enhancement MM06E001)
     PERFORM customer_function.
*   Außenhandelsdaten
*   Partnerzusatz für IMPINV01 ab Release 4.0A z.B. Zoll-ID-Nummer
     IF control_record_out-idoctp(6) EQ 'IMPINV'.
       PERFORM fill_e1edkaz.
     ENDIF.
   ENDIF.
*- Manuelle Anlieferungsanschrift, wenn in allen Positionen gleich ----
   IF pekko-adrnr NE space AND
      pekko-kunnr EQ space.
     CLEAR int_edidd.
     CLEAR e1edka1.
     int_edidd-segnam = 'E1EDKA1'.
can you please tell me how can control stoped at this code?
regards
niru

Migration CC and FF data from Virsa 4.0 to GRC 10.1 Data Inconsistency

Hello Guru's
We have done Migration from VIRSA 4.0 Compliance Calibrator (CC) and Firefighter (FF) data from to GRCAC 10.1 system.
After Migration, data inconsistency is coming while validation.
Followed standard sap migration guide virsa 4.0 to 10.0
Patch level - GRC AC 10.1 system
SAP_BASIS
740
0008
SAPKB74008
0000
@6H\QAchieved with Support Package@
SAP Basis Component
SAP_ABA
740
0008
SAPKA74008
0000
@6H\QAchieved with Support Package@
Cross-Application Component
SAP_GWFND
740
0008
SAPK-74008INSAPGWFND
0000
@6H\QAchieved with Support Package@
SAP Gateway Foundation 7.40
SAP_UI
740
0010
SAPK-74010INSAPUI
0000
@6H\QAchieved with Support Package@
User Interface Technology 7.40
PI_BASIS
740
0008
SAPK-74008INPIBASIS
0000
@6H\QAchieved with Support Package@
Basis Plug-In
ST-PI
740
0000
0000
SAP Solution Tools Plug-In
SAP_BW
740
0008
SAPKW74008
0000
@6H\QAchieved with Support Package@
SAP Business Warehouse
GRCFND_A
V1100
0006
SAPK-V1106INGRCFNDA
0000
@6H\QAchieved with Support Package@
GRC Foundation ABAP
GRCPINW
V1100_731
0006
SAPK-11506INGRCPINW
0000
@6H\QAchieved with Support Package@
SAP GRC NetWeaver Plug-In
IW_FNDGC
100
0002
SAPK-10002INIWFNDGC
0000
@6H\QAchieved with Support Package@
SAP IW FNDGC 100
WEBCUIF
747
0005
SAPK-74705INWEBCUIF
0000
@6H\QAchieved with Support Package@
SAP Web UI Framework
IW_CBS
200
0009
SAPK-20009INIWCBS
0000
@6H\QAchieved with Support Package@
SAP IW CBS 200
IW_CNT
200
0009
SAPK-20009INIWCNT
0000
@6H\QAchieved with Support Package@
SAP IW CNT 200
IW_SCS
200
0009
SAPK-20009INIWSCS
0000
@6H\QAchieved with Support Package@
Screen Scraping
POASBC
100_731
0001
SAPK-10201INPOASBC
0000
@6H\QAchieved with Support Package@
POA Shared Business Components
Patch level VIRSA 4.0 system
GRCPINW
V1100_731
0008
SAPK-11508INGRCPINW
SAP GRC NetWeaver Plug-In
Kindly let us know after migration, any sap notes need to install.
Regards,
karunakar

Hello Prasant,
We have migrated VIRSA 4 0 to GRC 10.1 system, after migration we have below issues.
1. In table GRACSODRISK (not able to see the medium risk, but in NWBC screen (Access Risks) we are seeing the medium risks.
2. In Function Permission.txt file ( only AND is coming for all, but some OR is avaiable in VIRSA 4 0 system.
And for gap (it automatically taken AND
Example:
AM02
FB02
F_BKPF_BED
ACTVT
2
AND
0
AM02
FB02
F_BKPF_BED
ACTVT
3
AND
1
AM02
FB02
F_BKPF_BED
BRGRU
AND
1
AM02
FB02
F_BKPF_BEK
ACTVT
2
AND
0
AM02
FB02
F_BKPF_BEK
ACTVT
3
AND
1
AM02
FB02
F_BKPF_BEK
BRGRU
AND
1
kindly suggest.
Regards,
Karunakar

Not able to map extension data type in standard namespace.

Hi guys,
I have a customer who has this problem. I am from the Business Partner area and BP supports XI for data exchange. We provide standard message types in XI which contains core BP fields in ABA namespace. Corresponding complex structure exists in the ABAP system.
Now, the customer has created an enhancement data type for one of the data types present in the standard message type. This enhancement data type is present in another namespace. The customer has also generated the proxy for this enhancement data type which automatically created an Append structure to the standard complex structure in ABAP.
Now, from the ABAP side all the data is extracted including the enhancement data into the complex structure. In one of the outbound function modules, we call XI passing this data in complex structure. However, we call XI in ABA namespace. So, in XI, since the ABA namespace does not contain the enhancement data type, the customer is not able to map this to his target. Even though we send all the data from ABAP to XI, since we call it in ABA namespace, the enhancement data is lost.
So, is there any way of mapping this enhancement data also in ABA namespace itself. Or from the ABAP, should I call the namespaces seperately. This means, first I will call ABA namespace to map all standard fields. Then, I call customer specific namespace to map enhancement data type.
I would really appreciate a help over here since its a very important customer for SAP.
Many thanks,
Vikram

I thing for customer mapping you have to do an mapping in our own namespace.
than you need a copy of the fb BUPA_OUTBOUND_MAIN an also from fb
ABA_BUPA_CALL_PROXY.
in the copy of ABA_BUPA_CALL_PROXY you can call your own proxy
do to changing this line
DATA : lo_ababusiness_partner_out TYPE REF TO co_ababusiness_partner_out ."XI.3.0
to
DATA :lo_ababusiness_partner_out TYPE REF TO yourproxy_mt
see also weblog /people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner

How to read data from the Deep structure.

Hi
How to get from the deep structure. Means i have one table in that having onother structure. i need to read data from that inner structure.
Regards
Reddy

Hi,
you can access in the way u use for the normal structure, u should only consider a deep structure is a table without headerline.
TABLES: BKPF, BSEG.
TYPES: TY_ITEM TYPE TABLE OF BSEG.
DATA:   BEGIN OF W_DOCUMENT,
                HEADER TYPE BKPF,
                ITEM       TYPE BSEG,
             END    OF W_DOCUMENT.
DATA: T_DOCUMENTS LIKE STANDARD TABLE OF W_DOCUMENT.
Insert the data:
SELECT * FROM BKPF WHERE ....
   W_DOCUMENT-HEADER = BKPF.
   SELECT * FROM BSEG INTO TABLE W_DOCUMENT-ITEM
                                   WHERE BUKRS = BKPF-BUKRS
                                        AND BELNR = BKPF-BELNR
                                        AND GJAHR = BKPF-GJAHR.
   APPEND W_DOCUMENT TO T_DOCUMENTS.
ENDSELECT.
Read the data:
LOOP AT T_DOCUMENTS INTO W_DOCMENT.
Header data
    WRITE: / W_DOCUMENT-HEADER-BUKRS,
                  W_DOCUMENT-HEADER-BELNR,
                  W_DOCUMENT-HEADER-GJAHR.
Item data
    LOOP AT W_DOCUMENT-ITEM INTO BSEG.
         WRITE: / BSEG-BUZEI,
                       BSEG-WRBTR CURRENCY W_DOCUMENT-HEADER-WAERS.
    ENDLOOP.
ENDLOOP.
Regards,
Padmam.

Can we enter data in any standard table directly through custom form??

Dear All,
Can we enter data in any standard table directly through custom form??
I have create custom form in R.12. I want to insert data in quality standard table directly through custom form. Need experts guideline.
Awaiting regards,

Hi,
Can we enter data in any standard table directly through custom form??
I have create custom form in R.12. I want to insert data in quality standard table directly through custom form. Need experts guideline.
Awaiting regards,
I would not recommend touching the standard tables at all unless you are being guided by the SR. For a record to be in the standard table it should go through series of validations based on the what operation you are performing and some times datas are dependent upon the other tables, and also some times the same records are hit to so many other tables simultaneously.
Therefore I would not recommend this brother.
Thanks &
Best Regards,

Why in SE16 we can not see New Data Table for standard DSO

Hi,
We says that there is three tables (New Data Table, Active Data Table and Change Log Table) of Standard DSO, Then Why in SE16 we can not see New Data Table of Standard DSO.
Regards,
Sushant

Hi Sushant,
It is possible to see the 3 DSO tables data in through SE16. May be you do not have authorization to see data through SE16.
Sankar Kumar

Ensure field sequence is correct for data for mutiple source structure

Hi,
I'm using LSMW with IDOC message type 'FIDCC2' Basic type 'FIDCCP02'.
I'm getting error that packed fields are not permitted.
I'm getting Ensure field sequence is correct for data for mutiple source structures.
Source Structures
       HEADER_STRUCT            G/L Account Document Header
           LINE_STRUCT              G/L Account Document Line
Source Fields
       HEADER_STRUCT             G/L Account Document Header
           BKTXT                          C(025)    Document Header Text
           BLART                          C(002)    Document Type
           BLDAT                          DYMD(008) Document Date
           BUDAT                          DYMD(008) Posting Date
           KURSF                          C(009)    Exchange rate
           WAERS                          C(005)    Currency
           WWERT                          DYMD(008) Translation Date
           XBLNR                          C(016)    Reference
           LINE_STRUCT               G/L Account Document Line
               AUFNR                          C(012)    Order
               HKONT                          C(010)    G/L Account
               KOSTL                          C(010)    Cost Center
               MEINS                          C(003)    Base Unit of Measure
               MENGE                          C(013)    Quantity
               PRCTR                          C(010)    Profit Center
               SGTXT                          C(050)    Text
               SHKZG                          C(001)    Debit/Credit Ind.
               WRBTR                          AMT3(013) Amount
I have changed PAC3 field for caracters fields of same length to avoid erreur message of no packed fields allowed.
Structure Relations
       E1FIKPF FI Document Header (BKPF)         <<<< HEADER_STRUCT G/L Account Document Header
               Select Target Structure E1FIKPF .
           E1FISEG FI Document Item (BSEG)          <<<< LINE_STRUCT   G/L Account Document Line
               E1FISE2 FI Document Item, Second Part of E1FISEG   (BSEG)
               E1FINBU FI Subsidiary Ledger (FI-AP-AR) (BSEG)
           E1FISEC CPD Customer/Vendor (BSEC)
           E1FISET FI Tax Data (BSET)
           E1FIXWT Extended Withholding Tax (WITH_ITEM)
Files
       Legacy Data          On the PC (Frontend)
           File to read GL Account info   c:\GL_Account.txt
                                          Data for Multiple Source Structures (Sequential Files)
                                          Separator Tabulator
                                          Field Names at Start of File
                                          Field Order Matches Source Structure Definition
                                          With Record End Indicator (Text File)
                                          Code Page ASCII
       Legacy Data          On the R/3 server (application server)
       Imported Data        File for Imported Data (Application Server)
           Imported Data                  c:\SYNERGO_CREATE_LCNA_FI_GLDOC_CREATE.lsmw.read
       Converted Data       File for Converted Data (Application Server)
           Converted Data                 c:\SYNERGO_LCNA_FI_GLDOC_CREATE.lsmw.conv
       Wildcard Value       Value for Wildcard '*' in File Name
Source Structures and Files
       HEADER_STRUCT G/L Account Document Header
                     File to read GL Account info c:\GL_Account.txt
           LINE_STRUCT G/L Account Document Line
                       File to read GL Account info c:\GL_Account.txt
File content:
Document Header Text     Document Type     Document Date     Posting Date     Exchange rate     Currency     Translation Date     Reference
G/L Account document     SA     20080401     20080409     1.05     CAD     20080409     Reference
Order     G/L Account     Cost Center     Base Unit of Measure     Quantity     Profit Center     Text     Debit/Credit Ind.     Amount
     44000022                    1040     Line item text 1     H     250
     60105M01     13431     TO     10          Line item text 2     S     150
800000     60105M01                         Line item text 3     S     100
     60110P01     6617     H     40          Line item text 4     S     600
     44000022                    ACIBRAM     Line item text 5     H     600
The file structure is as follow
Header titles
Header info
Line titles
Line1 info
Line2 info
Line3 info
Line4 info
Line5 info
Could someone direct me in the wright direction?
Thank you in advance!
Curtis

Hi,
Thank you so much for yout reply.
For example
i have VBAK(Heder structure)
          VBAP( Item Structure)
My file should be like this i think
Identification content         Fieldnames
     H                               VBELN      ERDAT     ERNAM
                                      Fieldvalues for header
      H                              1000          20080703   swapna
Identification content         Fieldnames
    I                                   VBELP     AUART
                                      Fieldvalues for item
    I                                  001             OR
                                       002             OR
Is this format is correct.
Let me know whether i am correct or not

How to read data from a CLUSTER STRUCTURE not cluster table.

Hi,
how to read data from a CLUSTER STRUCTURE not cluster table.
regards,
Usha.

Hello,
A structre doesnt contain data.. so u cannot read from it. U need to find out table of that structure and read data from it.
Regards,
Mansi.

How to fetch the data from a standard report to a user defined report

Hi,
i m using a standard report RFEBKA00 which uses CHAR300 variable(it is not used in selection screen).
can u help me ,
to collect the data from CHAR300 and to use it in my own report.
Message was edited by:
        jaya raman

hi   jayaramm..
you have to use SUBMMIT and send the parameters of your selection screen to the standard submmit prorgram...
beliow is the program for you .... just pick the selection parameter and pass corresponding parameter in the Submit which i mention as ...... replace with = and parameter in the selection screen.
report zrsers.
INCLUDE rfebka03.
INCLUDE rfebfr03.                      " Data France
INCLUDE RFEKAP00.                                          "n927883
TABLES: rfsdo,
        sscrfields,
        hrdeaoifld.
DATA: lt_statements TYPE STANDARD TABLE OF fieb_kukey,
      l_statement TYPE fieb_kukey.
*Daten für die Mahnsperre                                  "mo260105
TYPES: BEGIN OF s_kukey_mansp,
        sign(1),
        option(2),
        low TYPE kukey_eb,
        high TYPE kukey_eb,
        mansp TYPE mansp,
        anztg TYPE anztg,
        bukrs TYPE bukrs,
      END OF s_kukey_mansp.
DATA: lt_kukey TYPE STANDARD TABLE OF s_kukey_mansp,
      l_kukey LIKE LINE OF lt_kukey,
      l_gjahr TYPE gjahr,
      LT_GJAHR TYPE STANDARD TABLE OF GJAHR,
      L_MANSP TYPE MANSP,
      l_kunnr TYPE kunnr,
      l_lifnr TYPE lifnr.
FIELD-SYMBOLS: <mansp> LIKE LINE OF gt_mansp.
SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME TITLE text-165.
PARAMETERS:     einlesen     LIKE rfpdo1-febeinles,
                format       LIKE rfpdo1-febformat DEFAULT 'M' AS
                LISTBOX VISIBLE LENGTH 30 USER-COMMAND bai,
                AUSZFILE     LIKE RFPDO1-FEBAUSZF,
                umsfile      LIKE rfpdo1-febumsf,
                pcupload     LIKE rfpdo1-febpcupld DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK 1.
*------- Buchungsparameter ---------------------------------------------
SELECTION-SCREEN BEGIN OF BLOCK 2 WITH FRAME TITLE text-160.
*SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: pa_xcall TYPE febpdo-xcall    RADIOBUTTON GROUP 1.
*SELECTION-SCREEN
* COMMENT 03(29) FOR FIELD pa_xcall.
PARAMETERS: pa_xbkbu TYPE febpdo-xbkbu.
*SELECTION-SCREEN
* COMMENT 35(16) text-171 FOR FIELD pa_xbkbu.
PARAMETERS: pa_mode TYPE rfpdo-allgazmd NO-DISPLAY.
*SELECTION-SCREEN: END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: pa_xbdc LIKE febpdo-xbinpt   RADIOBUTTON GROUP 1.
SELECTION-SCREEN
COMMENT 03(29) text-163 FOR FIELD pa_xbdc.
SELECTION-SCREEN
COMMENT 35(20) text-164 FOR FIELD mregel.
PARAMETERS: mregel   LIKE rfpdo1-febmregel DEFAULT '1'.
SELECTION-SCREEN: END OF LINE.
SELECTION-SCREEN: BEGIN OF LINE.
PARAMETERS: pa_test LIKE rfpdo1-febtestl RADIOBUTTON GROUP 1.
SELECTION-SCREEN
COMMENT 03(29) text-168 FOR FIELD pa_test.
SELECTION-SCREEN: END OF LINE.
PARAMETERS: valut_on     LIKE rfpdo2-febvalut DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK 2.
*------- Finanzdisposition ---------------------------------------------
SELECTION-SCREEN BEGIN OF BLOCK 5 WITH FRAME TITLE text-172.
SELECTION-SCREEN: BEGIN OF LINE.
PARAMETERS: pa_xdisp LIKE febpdo-xdisp.
SELECTION-SCREEN
COMMENT 03(29) text-170 FOR FIELD pa_xdisp.
PARAMETERS: pa_verd LIKE rfffpdo1-ffdisxverd.
SELECTION-SCREEN
COMMENT 34(15) text-174 FOR FIELD pa_verd.
SELECTION-SCREEN
COMMENT 55(15) text-173 FOR FIELD pa_dsart.
PARAMETERS: pa_dsart LIKE fdes-dsart.
SELECTION-SCREEN: END OF LINE.
PARAMETERS: intraday     LIKE rfpdo1_en-akintraday AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK 5.
*C5060356
*------- BAI Preprocessor --------------------------------------
SELECTION-SCREEN BEGIN OF BLOCK 6 WITH FRAME TITLE text-007 .
PARAMETERS:     p_baipre   TYPE bai_prep AS CHECKBOX MODIF ID mo1,
                p_priord   LIKE prior_day AS CHECKBOX MODIF ID mo1,
                p_stop     LIKE stop_flag AS CHECKBOX MODIF ID mo1.
SELECTION-SCREEN END OF BLOCK 6.
*------- Interpretationsparameter --------------------------------------
SELECTION-SCREEN BEGIN OF BLOCK 3 WITH FRAME TITLE text-166.
DATA: num10(10) TYPE n.
DATA: chr16(16) TYPE c.
SELECT-OPTIONS: s_filter FOR febpdo-febfilter1.
SELECT-OPTIONS: t_filter FOR febpdo-febfilter2.
SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN
   COMMENT 01(31) text-176 FOR FIELD pa_bdart.
PARAMETERS: pa_bdart     LIKE febpdo-bdart.
SELECTION-SCREEN
   COMMENT 36(21) text-177 FOR FIELD pa_bdanz.
PARAMETERS: pa_bdanz     LIKE febpdo-bdanz.
SELECTION-SCREEN: END OF LINE.
SELECTION-SCREEN END OF BLOCK 3.
*------- Ausgabeparameter ----------------------------------------------
SELECTION-SCREEN BEGIN OF BLOCK 4 WITH FRAME TITLE text-167.
PARAMETERS: batch        LIKE rfpdo2-febbatch,
            p_koausz     LIKE rfpdo1-febpausz,   " Kontoauszug drucken
            p_bupro      LIKE rfpdo2-febbupro,
            p_statik     LIKE rfpdo2-febstat,
            pa_lsepa     LIKE febpdo-lsepa.
SELECTION-SCREEN END OF BLOCK 4.
SUBMIT RFEBKA00
        WITH AUSZFILE = AUSZFILE   ***like this replace the .... and pass selection parameters
        WITH BATCH = BATCH
        WITH EINLESEN ...
        WITH FORMAT ...
        WITH INTRADAY ...
        WITH MREGEL ...
        WITH PA_BDANZ ...
        WITH PA_BDART ...
        WITH PA_DSART ...
        WITH PA_LSEPA ...
        WITH PA_MODE ...
        WITH PA_TEST ...
        WITH PA_VERD ...
        WITH PA_XBDC ...
        WITH PA_XBKBU ...
        WITH PA_XCALL ...
        WITH PA_XDISP ...
        WITH PCUPLOAD ...
        WITH P_BAIPRE ...
        WITH P_BUPRO ...
        WITH P_KOAUSZ ...
        WITH P_PRIORD ...
        WITH P_STATIK ...
        WITH P_STOP ...
        WITH S_FILTER ...
        WITH T_FILTER ...
        WITH UMSFILE ...
        WITH VALUT_ON = VALUT_ON   and return .
reward points if it is usefull
Girish

Error in Loading FIGL data into a standard ODS

Hi,
I have encountered an error when i attempted to load FIGL data into a standard ODS. Below is the error i received:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Second step in the update
Second step in the update
Second step in the update
Second step in the update
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
Initially i discovered a work around wherein i loaded the data into a write optimize ODS. It was successful. However, when i attempted to data mart the data and put it into a standard ODS, the similar error occurred.
Please help me with this problem.
Ramon

Hi,
Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the new data table.
Thanks,
JituK

XML Data Load into releational structures

Hi,
I am very unexperienced in using XML and have the problem
to import very large XML data files into existing reletional structures.
In our production DB we don't use the java engine, so
that PL/SQL an the SQL Loader are the only available ways to import the data.
At the moment we get flat files and use the SQL Loader utility. But an interface to a new system send XML data now and I have to fill the same old releational structure with the new data.
Can anybody give me a hint about the best technic for an high performance import. Are there any existing tools for the relational mapping?
Regards Ralph

Thank you for your reply.
You are right. We only want to break the XML to fill our relational structures. We don't need the XML data further on. But we have to load the data in temporary structures, because we have to transform the data in our own format. (The system which delivers the XML data is external and uses another data model)
Is there no more elegant way with use of databse built in technics? The XML data we get can be validated against a XML schema.
So I thought, it could be a way to load the XML in the XDB and register the schema in the database. After that store the XML data in the default generated object relational structures and then programm the data transformation and the data flow between these default structures to our target data structures with PL/SQL.
I don't know if this way is performant enough.
If I use an external tool i have to code the relational mapping outside the database and insert the data with use of ODBC in temporary structures which i have to create manualy.
So I hoped to find a way to load the data in any relational structure using the advantages of XML and XML schema and code the neccasary logic inside the DB.
Do you have any further hints for my problem?
Regards Ralph

Data inconsistency: posting with restricted transaction type (FAA_POST047)

Hi colleagues!
I have the following error:
Data inconsistency: posting with restricted transaction type
Message no. FAA_POST047
Diagnosis
You are trying to post in company code 1000 with transaction type 130 in ledger group 0N. According to table TABWA, this transaction type is limited. Nonetheless, according to your entries, you want to post to area 11.
System Response
Using limited transaction types is obsolete and would lead to an inconsistent posting in this situation. The system rejects the posting.
Procedure
Use a transaction type that is not limited. And, if possible, choose the ledger group and/or depreciation area on the initial screen.
According to specific accounting we shouldn't post to one of the depr. area, so most of the tr.types are restricted to post to all areas except this one.
Because of this, posting from MM with acc.assignment 'A' is impossible - I have this error.
Any ideas how to solve?
Thanks in advance

Hi Anton
This looks like your transaction type -130 is limited to post only in ledger group-0N as per the transaction type configuration. Due to which system is unable to post all the ledgers and hence this lead to inconsistency.
Please verify the transaction type 130- in configuration T code - OAYA and see if it is restricted by depreciation area (eventually allow to post only ledger group- 0N.
Tcode - OAYA (Limit Transaction Types to Depreciation Areas)
please verify and let us know the update. hope this helps
Best Regards
Jomon

Idoc data in flat file structure

Dear Experts,
We have idoc data in flat file structure. We need to fetch it using ftp and map it to an idoc.
please tell me how to proceed .
Thanks,
Aju

Hi,
For flat file you need to use the File content conversion parameters.
Refer the blog,
SAP Network Blog: How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
Thanks
Swarup

Error when activate standard structure

Hi guru,
i've a serious problem about the activation of a standard structure,the check (for error) pass without problem, but when I want to activate it there is this exception :
CALL SCREEN (not modal) in modal dialog box not allowed
Anybody can help me ?
Thanks.
Angelo.
Edited by: Angelo Abbasci on Jan 13, 2009 2:52 PM

HI,
I try but cant do much as it is a standard structure..
You could try to change the structure save it. The n execute the transaction again and try to activate..
You added the field with Access Key or through Append structure..?
If you get the error again then try and copy paste the error report important parts..

Data Inconsistent at Standard Structure IS_BIL_INVOICE-IT_GEN

Similar Messages

Maybe you are looking for