Issue with data while uploading data form cube 0COOM_C02

hi,
i am uploading data from infocube 0COOM_C02(costs cube).
the infocube receives the data from infosources 0COOM_CCA_9 and 0COOM_OPA_6.
While i transfer the data records from the infocube 0COOM_C02 to another Zcube of the same structure as the prior one via data mart.
isee that some of the data records are missing and the total costs for a costcenter is different in both infocubes.
has some has faced similar issue before??? are there any prerequisites before the data from costs cube 0COOM_C02 to be transferred to another cube via data mart.
pls clarify
Subramanian

Hello Scooby,
The number of records are bound to be less as there is a aggregation across request ids happening in the target z cube while in the lower cube the requests are not getting aggregated ..
Best and the only way to check is to use a query and check result sets by including and excluding the requids.
Please dont forget to grant some points ..
Regards
Nikhil

Similar Messages

Problem while uploading data with GUI UPLOAD Function

Hi,
I am facing problem while uploading data with FM GUI UPLOAD in out text file there are 7 row but after the FM GUI UPLOAD there are 14 entries are coming in Internal table and each alternate row is coming as blank with 0000 in some column in internal table first row is proper and second line is blank so on.
what can be the problem .
The program in which we are using this we are using it from last 2 year but we are facing problem today only.
regards,
zafar

Hi,
The file formate is same as it is from last two years it is automatically generated by one another bar code server and there is no change in the file formate.
So waht can be the problem to check any inconsistancy in system i have develop a samll program fro uploading a text file with same function module , but it is working fine.
regards,
zafar

DB Connect Load - "Unknow error while uploading data from the DB Table"

Hi Experts,
We have our BI7 system connected to Oracle DB based third party tool. The loads are performing quite well in DEV environment.
I would like to know, how we transport DB Connect datasources to Quality systems? Any different process to be followed for DB Connect datasources?
At present the connections between BI Quality and the third party quality systems are established. We transported the DataSource from BI DEV system to BI quality system, but on trigerring an infopackage we are not able to perform loads. It prompts - "Unknow error while uploading data from the DB Table".
Also on comparing the DataSources in DEV system and Quality system there are no fields in "Proposal" tab of datasource in Quality system. Also I cannot change or activate Datasource in Quality system as we dont have change access in quality.
Please advice.
Thanks,
Abhijit

Hi,
Sorry for bumping an old thread ....
Did this issue get ever get resolved?
I am facing the same one. The loads work successfully in Dev. The transport for DBConnect DS also moved in successfully.
One strange this is that DB User for dev did not automatically change to db user from quality when I transported the DBConnect datasource. DBCon DS still shows me the DB User from Dev in Quality system
I get "Unknown Error" whenever I trigger the data package.
Advait

What are the difficulties that we face while uploading data in lsmw

what are the difficulties that we face while uploading data in lsmw

I've used LSMW extensively for all implementation projects. Most complex problem is when you have to deal with a lot of structures (for example in routings), where you have header/line item/sub-items/long texts/etc relationship. Still, LSMW can pull it fine.

Random Records are being skipped while uploading data in PSA from CSV File

Hi Experts,
I am facing issue in data uploading in PSA through CSV file, Random Records are being skipped while uploading data in PSA.
First Load
We have flat file (.txt in CSV format), which contains 380240 Records.
We are uploading the flat file data into PSA from Application Server. But it uploads Only 380235 records, 5 Records are being skipped.
Second Load
We have re-generated same file next day, which contains same No of Records (380240), but this time it uploads Only 380233 records, 7 Records are being skipped.
We found 1 skipped record (based on key columns combination, by cross verifying from source and PSA table) from First load. But same records (combination of key column) is available in second load. It means same records are not being skipped every time.
Earlier (5 months ago) , We have loaded 641190 Records from flat file in same PSA and all records (641190) were uploaded successfully.
There is no change is Source, PSA and flat file structure.
Thanks & Regards
Bijendra

Hi Bijendra,
Please check in the file if at the begining if it has got any excape sign then that record may be skipped so the records may be mssing
Please check the excape sign like ; if they are present at the beginign that recor entirely will be skipped.
Regards
vamsi

While uploading data into the r/3 using call transaction or session method

hi experts
while uploading data into the r/3 using call transaction or session method error occured in the middle of the processing then how these methods behaves it transfers next records or not?

hai
Session method: The records are not added to the database until the session is processed. sy-subrc is not returned. Error logs are created for error records. Updation in database table is always Synchronous.
Call Transaction method: The records are immediately added to the database table. sy-subrc is returned to 0 if successful. Error logs are not created and hence the errors need to be handled explicitly. Updation in database table is either Synchronous or Asynchronous.
While to transfer the data from the through if any errors occurs until the errors are the complete the data is not transfer to the SAP system.
the system compulsory shows the errors. that errors are stored into the error logs (Transaction is SM35).
so the session method should not return any value.
In call transaction method data is directly pass to the SAP system.
So its compulsory return the value.
Because of the call transaction is the function.
A function should return the value mandatory
In session method errors stroed in SYSTEM GENRATED ERROR LOG.
IN CALL TRANSACTION TO CAPTURE THE ERRORS WE SHOULD PERFORM THE FOLLOWING.
FIRST ME MUST DECLARE AN INTERNAL TABLE WITH THE STRUCTURE OF BDCMSGCOLL TABLE.
THEN WHILE WRITING THE CALL TRANSACTION STATEMENT WE SHOULD PUT THE 'E' MODE FOR CAPTURING ALL THE ERRORS.
THEN FINALLY THE CAPTURED ERRORS MUST TO SENT TO THE INTERNAL TABLE WHICH WE DECLARED IN THE BEGINNING WITH BDCMSGCOLL BY USING THE FUNCTION MODULE "FORMAT_MESSAGE"
AND THUS THE ERROR MESSAGES WILL BE SENT TO THE INTERNAL TABLE WHICH WE DECLARED AT THE BEGINNING.

Error while uploading data in table t_499s through BDC Prog

Hi
am facing problem while uploading data in table t_499s through BDC Program , if there is more than 15 records in file its not allowing to upload kindly suggest what to do
Thanx
Mukesh s

Hi,
See if you want to update only single table, which has User maintenance allowed
Use Modify statement.
EX:
LOOP AT ITAB INTO WA_TAB.
    MOVE-CORRESPONDING WA_TAB TO T499S.
    MODIFY T499S.
    CLEAR T499S.
ENDLOOP.
It will update the table, to check go to sm30 , and check in V_T499S.
Rgds
Aeda

Error in Source System While Uploading Data from ODS to Data Target

Hi All,
Iam getting Following Error while Uploading data from ODS to Data Target
a) Error in Source System.
b)DataSource 80MKT_DS01 has to be replicated (time stamp, see long text)
Message no. R3016
Diagnosis
DataSource 80MKT_DS01 does not have the status of the source system in the Business Information Warehouse.
The time stamp in the source system is 21.06.2005 07:31:33.
The time stamp in the BW system is 27.11.2004 17:41:45.
Regards,
Chakri

This generally occurs when you change the data source or enhance the data source or the coonections to the datasoiurse are broken. To resdolve thius sort of errors just
1. Check for the coonect between the sourse & target systems
2 . Replicate the data sourcses.
3. Acivated TR,UR,& the rest of the flow But check in the source system if the structre is modified & is so do the changes in the IS , TR,UR correspondingly & the try to load .Hoppe it allows you to load .
Thanks ,
PSG

Issue with Oracle LONG RAW data type

Hi All,
I am facing some issues with Oracle LONG RAW DATA Type.
We are using Oracle 9IR2 Database.
I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
I have gone through some docs and found we should not use LONG RAW using these operations.
So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
Appreciate if anyone can help me out here.
DECLARE
Y LONG RAW;
BEGIN
FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
INSERT INTO TRU_CMP.TERRITORY
BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
VALUES
REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
REC.STARTPERIOD, REC.TERRITORYSEQ
END LOOP;
END;
/

Maddy wrote:
Hi All,
I am facing some issues with Oracle LONG RAW DATA Type.
We are using Oracle 9IR2 Database.
I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
I have gone through some docs and found we should not use LONG RAW using these operations.
So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
Appreciate if anyone can help me out here.
DECLARE
Y LONG RAW;
BEGIN
FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
INSERT INTO TRU_CMP.TERRITORY
BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
VALUES
REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
REC.STARTPERIOD, REC.TERRITORYSEQ
END LOOP;
END;
/below might work
12:06:23 SQL> help copy
COPY
Copies data from a query to a table in the same or another
database. COPY supports CHAR, DATE, LONG, NUMBER and VARCHAR2.
COPY {FROM database | TO database | FROM database TO database}
            {APPEND|CREATE|INSERT|REPLACE} destination_table
            [(column, column, column, ...)] USING query
where database has the following syntax:
     username[/password]@connect_identifier

While uploading data from local file

Hi,
While uploading data from local file having the header text into interal table using the GUI_UPLOAD function module,there is problem in upload because of header text in file, do we have any option in this FM itself to skip this header text and upload from sdecond line because as per our requirement we can't delete this header text from the file.

Hi Manish,
Do you have the problem while uploading? Is it giving any error?
If not, if your uploading is successful into the internal table, then delete the first row, which is header, from the internal table using index eq 1.
Regards,
Chandra Sekhar

Error while uploading infopath forms

Hi,
I am facing one issue while uploading infopath form through central admin form is getting stuck with upgrading .It is not new form just uploding a copy after removing one control on the form
I tried following things
1.Running the stsadm -o execadmsvcjobs
2.Restaring SPAdmin,SP Timer
3.Restarting IIS
I have only one web front end server.We have few days back installed service pack2 on that server .Can any one advice ??

Hi,
Go to "Local Service" and make sure that SharePoint Administration server is running or restart it. All upgrade activities are handled by that service.
Magnus Danielson

Issue with LCM while migrating planning application in the cluster Env.

Hi,
Having issues with LCM while migrating the planning application in the cluster Env. In LCM we get below error and the application is up and running. Please let me know if anyone else has faced the same issue before in cluster environment. We have done migration using LCM on the single server and it works fine. It just that the cluster environment is an issue.
Error on Shared Service screen:
Post execution failed for - WebPlugin.importArtifacts.doImport. Unable to connect to "ApplicationName", ensure that the application is up and running.
Error on network:
“java.net.SocketTimeoutException: Read timed out”
ERROR - Zip error. The exception is -
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)

Hi,
First of all, if your environment for source and target are same then you will have all the users and groups in shared services, in that case you just have to provision the users for this new application so that your security will get migrated when you migrate the from the source application. If the environs are different, then you have to migrate the users and groups first and provision them before importing the security using LCM.
Coming back to the process of importing the artifacts in the target application using LCM, you have to place the migrated file in the @admin native directory in Oracle/Middleware/epmsystem1.
Open shared services console->File system and you will see the your file name under that.
Select the file and you will see all your exported artifacts. Select all if you want to do complete migration to target.
Follow the steps, select the target application to which you want to migrate and execute migration.
Open the application and you will see all your artifacts migrated to the target.
If you face any error during migration it will be seen in the migration report..
Thanks,
Sourabh

Is anyone else having issues with "skipping" while the songs are playing?! It is very aggravating to us... and we've had it going on for several months now. Any ideas at all how to fix it?

Is anyone else having issues with "skipping" while the songs are playing?! It is very aggravating to us... and we've had it going on for several months now. Any ideas at all how to fix it?

So, don't use youtube.
http://www.the-top-tens.com/lists/best-alternatives-youtube.asp
http://www.youtubealternative.com/

While uploading data for employee as a vendor (with their loans and advance

Hi,
We are going for one company live. We are not taking HR module as of now.
We are creating employee as a vendor for all employees with outstanding loans and advances.
Now while uploading initial data for these employee (created as vendor), business wants personal loan outstanding balances employee as a vendor wise.
Generally in case of normal vendor, we treat like
Vendor A/C Dr
to takeover creditors a/C Cr
while going for initial upload.
In above case what should we do if we want outstanding balances (personal loan) while initial balance upload?
Thanks,
Taral Patel

Hi,
You can create a separate employee vendor for Advances paid to them with an assignment to a separate recon account titled as Advance to Employees. Later, you can upload the entries by Debiting the Employee Advance Vendor account and crediting Vendor Upload Account.
Advances paid to employees (recon account) will represent in the TB as a separate line item forming an MIS.
Regards
Hari

Problem with direct input program while uploading data into database

TABLES: BGR00,                        " Mappensatz
         BMM00,                        " MM01/MM02 BTCI-Kopfdaten
         BMMH1,                        " MM01/MM02 Hauptdaten
         BMMH2,                        " Länderdaten (Steuern)
         BMMH3,                        " Prognosewerte
         BMMH4,                        " Verbrauchswerte
         BMMH5,                        " Kurztexte
         BMMH6,                        " Mengeneinheiten
         BMMH7,                        " Langtexte
         BMMH8.                        " Referentielle EAN's
       Satztypen
DATA:    MAPPENSATZ LIKE BMM00-STYPE VALUE '0',
         KOPFSATZ    LIKE BMM00-STYPE VALUE '1',
         HAUPTSATZ   LIKE BMM00-STYPE VALUE '2',
         KUN_SATZ    LIKE BMM00-STYPE VALUE 'Z',
         LANDSATZ    LIKE BMM00-STYPE VALUE '3',
         PROGSATZ    LIKE BMM00-STYPE VALUE '4',
         VERBSATZ    LIKE BMM00-STYPE VALUE '5',
         KTEXTSATZ   LIKE BMM00-STYPE VALUE '6',
         MESATZ      LIKE BMM00-STYPE VALUE '7',
         TEXTSATZ    LIKE BMM00-STYPE VALUE '8',
         EANSATZ     LIKE BMM00-STYPE VALUE '9'.
Common Data Bereich fuer die extern aufgerufenen Routinen
       Initialstrukturen
DATA: BEGIN OF COMMON PART RMMMBIMY.
DATA:    BEGIN OF I_BMM00.
           INCLUDE STRUCTURE BMM00.    " Kopfdaten
DATA:    END OF I_BMM00.
DATA:    BEGIN OF I_BMMH1.
           INCLUDE STRUCTURE BMMH1.    " Haupdaten
DATA:    END OF I_BMMH1.
DATA:    BEGIN OF I_BMMH2.
           INCLUDE STRUCTURE BMMH2.    " Länderdaten
DATA:    END OF I_BMMH2.
DATA:    BEGIN OF I_BMMH3.
           INCLUDE STRUCTURE BMMH3.    " Prognosewerte
DATA:    END OF I_BMMH3.
DATA:    BEGIN OF I_BMMH4.
           INCLUDE STRUCTURE BMMH4.    " Verbrauchswerte
DATA:    END OF I_BMMH4.
DATA:    BEGIN OF I_BMMH5.
           INCLUDE STRUCTURE BMMH5.    " Kurztexte
DATA:    END OF I_BMMH5.
DATA:    BEGIN OF I_BMMH6.
           INCLUDE STRUCTURE BMMH6.    " Mengeneinheiten
DATA:    END OF I_BMMH6.
DATA:    BEGIN OF I_BMMH7.
           INCLUDE STRUCTURE BMMH7.    " Textzeilen
DATA:    END OF I_BMMH7.
DATA:    BEGIN OF I_BMMH8.
           INCLUDE STRUCTURE BMMH8.    " Referentielle EAN's
DATA:    END OF I_BMMH8.
DATA: END OF COMMON PART.
DATA: WA LIKE TEDATA-DATA.
       Einzelfelder
DATA:    GROUP_COUNT(6) TYPE C,    " Anzahl Mappen
         TRANS_COUNT(6) TYPE C,    " alte Definition für rmmmbim0
         SATZ_COUNT LIKE MUEB_REST-TRANC, " Trans.zähler neu
         H_IND_COUNT LIKE MUEB_REST-D_IND, " Index welches Feld zurücks.
         SATZ2_COUNT(6) TYPE C.    " Anz. Sätze je Trans. ohne Kopfsatz
DATA:    XEOF(1)          TYPE C, " X=End of File erreicht
         XHAUPTSATZ_EXIST TYPE C, " X=Hauptsatz zum Kopf exi.
         NODATA(1)        TYPE C. " kein BI für dieses Feld
mk/15.08.94:
DATA:    GROUP_OPEN(1) TYPE C.             " X=Mappe schon geöffnet
*eject
       Konstanten
DATA:    C_NODATA(1)    TYPE C VALUE '/'.   " Default für NODATA
DATA:    MATNR_ERW     LIKE MARA-MATNR VALUE '0                 '.
DATA:    MATNR_ERW_INT LIKE MARA-MATNR. "internal sight of '0      '
DATA:    MATNR_LAST    LIKE MARA-MATNR. "Material number
mk/11.08.94 2.1H:
If this flag is initial, the database updates will be done directly
during background maintenance instead of using a separate update
task. (no usage of this flag in dialogue mode!)
DATA: DBUPDATE_VB(1) VALUE ' '.       "note 306628
data: matsync type mat_sync. "wk/99a no update in dialog if called
***INCLUDE ZMUSD070.
TABLES: MARA,                          "Material Master: General Data
        MARC,                          "Material Master: C Segment
        MARD,                          "Material Master: St Loc/Batch
        MBEW,                          "Material Valuation
        MVKE,                          "Material Master: Sales Data
        MLGN,                          "Material Data per Whse Number
        MLAN,                          "Tax Classification: Material
        T001W,                         "Plants/Branches
        TBICU.
DATA: BEGIN OF VALUTAB OCCURS 0.
        INCLUDE STRUCTURE RSPARAMS.
DATA: END OF VALUTAB.
DATA: BEGIN OF VARTECH.
        INCLUDE STRUCTURE VARID.
DATA: END OF VARTECH.
DATA: PARMS LIKE ZXXDCONV.
DATA: REC_COUNT      TYPE I,
      REC_COUNT_BAD TYPE I,
      ZJOBID         LIKE TBIZU-JOBID,
      ZJOBCOUNT      LIKE TBIZU-JOBCOUNT,
      ZMATNR         LIKE MARA-MATNR,
      ZTEXT(80)      TYPE C.
CONSTANTS: LIT_ZERO(18) TYPE C            VALUE '000000000000000000',
           LIT_CHAR      TYPE C            VALUE '_',
           LIT_CREATE    LIKE BMM00-TCODE VALUE 'MM01',
           LIT_CHANGE    LIKE BMM00-TCODE VALUE 'MM02',
           LIT_CHECK(1) TYPE C            VALUE 'X'.
DATA: BEGIN OF INP_DATA OCCURS 0,
         MATNR(18) TYPE C,            " Material code
         UMREN(6)   TYPE C,            " Denominator
         MEINH(3)   TYPE C,            " Alternate UOM
         UMREZ(6)   TYPE C,            " Numerator
       END OF INP_DATA.
*eject
SELECTION-SCREEN BEGIN OF BLOCK INOUT WITH FRAME TITLE TEXT-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (13) TEXT-004.
PARAMETERS:     P_PC        RADIOBUTTON GROUP SRC DEFAULT 'X'.
SELECTION-SCREEN COMMENT (6) TEXT-005.
PARAMETERS:     P_UNIX      RADIOBUTTON GROUP SRC.
SELECTION-SCREEN COMMENT (6) TEXT-006.
PARAMETERS:     P_DS_TYP    LIKE     ZXXDCONV-DS_TYP
                               DEFAULT 'ASC'.
SELECTION-SCREEN END OF LINE.
*SELECT-OPTIONS: S_PATH      FOR      PARMS-PATH
                              NO INTERVALS
                              LOWER CASE.
PARAMETERS: P_PATH TYPE RLGRAP-FILENAME.
PARAMETERS:     P_HDRLIN   LIKE     ZXXDCONV-HDR_LINES
                               DEFAULT 0,
                P_JOBNAM   LIKE     TBICU_S-JOBNAME
                               MEMORY ID BM1,
                P_DI_EXE    AS       CHECKBOX
                               DEFAULT LIT_CHECK,
                P_MAPPE     LIKE     BGR00-GROUP
                               DEFAULT 'MRP_UOM_LOAD'
                               NO-DISPLAY.
SELECTION-SCREEN END OF BLOCK INOUT.
*eject
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_PATH.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            PROGRAM_NAME = SYST-REPID
            DYNPRO_NUMBER = SYST-DYNNR
            FIELD_NAME    = 'P_PATH'
       CHANGING
           FILE_NAME     = S_PATH-LOW
            FILE_NAME     = P_PATH
       EXCEPTIONS
            MASK_TOO_LONG = 1
            OTHERS        = 2.
AT SELECTION-SCREEN.
Set up parameter record
PARMS-UNIX      = P_UNIX.
PARMS-PC        = P_PC.
PARMS-DS_TYP    = P_DS_TYP.
PARMS-JOBNAME   = P_JOBNAM.
PARMS-MAPPE     = P_MAPPE.
PARMS-HDR_LINES = P_HDRLIN.
*eject
       Main Processing Routine                                       *
START-OF-SELECTION.
Initialization
PERFORM 0000_HOUSEKEEPING.
Initialize transaction data in I_BM00
PERFORM 0500_INIT_BMM00.
Process input files
SORT S_PATH BY SIGN OPTION LOW.
     MOVE S_PATH-LOW TO PARMS-PATH.
      MOVE P_PATH TO PARMS-PATH.
LOOP AT S_PATH.
   AT NEW LOW.
      CLEAR   INP_DATA.
     REFRESH INP_DATA.
Read source data into internal table
      PERFORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
Processs each record in internal table
      ZTEXT    = TEXT-007.
      ZTEXT+13 = PARMS-DS_NAME.
      PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
Initialize transaction data in I_BM00
PERFORM 0500_INIT_BMM00.
      LOOP AT INP_DATA.
Reset tables for each record
        BMM00              = I_BMM00.
        BMMH1              = I_BMMH1.
        BMMH6              = I_BMMH6.
Load structures with data
        MOVE-CORRESPONDING INP_DATA TO BMM00.
        PERFORM 2000_WRITE_OUTPUT USING BMM00.
        MOVE-CORRESPONDING INP_DATA TO BMMH1.
        PERFORM 2000_WRITE_OUTPUT USING BMMH1.
        MOVE-CORRESPONDING INP_DATA TO BMMH6.
        PERFORM 2000_WRITE_OUTPUT USING BMMH6.
        REC_COUNT = REC_COUNT + 1.
      ENDLOOP.
   ENDAT.
ENDLOOP.
IF REC_COUNT GT 0
AND P_DI_EXE EQ LIT_CHECK.
    PERFORM 3000_START_DI_JOB.
ENDIF.
WRITE: / TEXT-008,
           REC_COUNT.
PERFORM 9000_END_OF_JOB.
*eject
Include containing common routines used by direct input programs
INCLUDE ZMUSD071.
*eject
      FORM 0500_INIT_BMM00                                          *
      Initialize I_BMM00 with transaction code and views selected   *
FORM 0500_INIT_BMM00.
***this changes done by samson**
if not inp_data[] is initial.
select single matnr from mara INTO ZMATNR where matnr = inp_data-matnr.
if sy-subrc = 0.
I_BMM00-TCODE = LIT_CHANGE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
else.
I_BMM00-TCODE = LIT_CREATE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
endif.
endif.
**this changes above done by samson**
Transaction code
I_BMM00-TCODE = LIT_CHANGE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
ENDFORM.
INCLUDE ZMUSD069.
*eject
      FORM 0000_HOUSEKEEPING                                        *
      Initialization routines                                       *
FORM 0000_HOUSEKEEPING.
PERFORM 0010_LDS_NAME.
PERFORM 0020_DS_NAME.
PERFORM 0030_OPEN_FILE.
PERFORM 0040_INIT_STRUCTS.
ENDFORM.
*eject
      FORM 0010_LDS_NAME                                            *
      Obtain logical file name from DI job details                  *
FORM 0010_LDS_NAME.
Check valid job name
SELECT SINGLE * FROM TBICU
                  WHERE JOBNAME EQ PARMS-JOBNAME.
IF SY-SUBRC EQ 0.
    CALL FUNCTION 'RS_VARIANT_VALUES_TECH_DATA'
         EXPORTING
              REPORT               = TBICU-REPNAME
              VARIANT              = TBICU-VARIANT
         IMPORTING
              TECHN_DATA           = VARTECH
         TABLES
              VARIANT_VALUES       = VALUTAB
         EXCEPTIONS
              VARIANT_NON_EXISTENT = 1
              VARIANT_OBSOLETE     = 2
              OTHERS               = 3.
    IF SY-SUBRC EQ 0.
      READ TABLE VALUTAB WITH KEY 'LDS_NAME'.
      MOVE VALUTAB-LOW TO PARMS-LDS_NAME.
    ELSE.
      MESSAGE I001 WITH PARMS-JOBNAME.
      MESSAGE A099.
    ENDIF.
ELSE.
    MESSAGE I000 WITH PARMS-JOBNAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 0040_INIT_STRUCTS                                        *
      Initialize structures for direct input records                *
FORM 0040_INIT_STRUCTS.
Start of standard SAP initialization from example program RMMMBIME
*------- Write session record -
CLEAR BGR00.
BGR00-STYPE = MAPPENSATZ.
BGR00-GROUP = PARMS-MAPPE.
BGR00-NODATA = C_NODATA.
BGR00-MANDT = SY-MANDT.
BGR00-USNAM = SY-UNAME.
BGR00-START = BGR00-NODATA.
BGR00-XKEEP = BGR00-NODATA.
PERFORM 2000_WRITE_OUTPUT USING BGR00.
*----- Initialize structures -
NODATA = BGR00-NODATA.
PERFORM INIT_STRUKTUREN_ERZEUGEN(RMMMBIMI) USING NODATA.
End of standard SAP initialization from example program RMMMBIME
ENDFORM.
*eject.
      FORM 3000_START_DI_JOB                                        *
      Start direct input job                                        *
FORM 3000_START_DI_JOB.
ZTEXT = 'Starting '(021).
ZTEXT+9 = TBICU-JOBNAME.
PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
CALL FUNCTION 'BI_START_JOB'
       EXPORTING
            JOBID                 = ' '
            JOBTEXT               = TBICU-JOBNAME
            REPNAME               = TBICU-REPNAME
            SERVER                = TBICU-EXECSERVER
            VARIANT               = TBICU-VARIANT
            NEW_JOB               = 'X'
            CONTINUE_JOB          = ' '
            START_IMMEDIATE       = 'X'
            DO_NOT_PRINT          = 'X'
            USERNAME              = SY-UNAME
       IMPORTING
            JOBID                 = ZJOBID
            JOBCOUNT              = ZJOBCOUNT
       EXCEPTIONS
            JOB_OPEN_FAILED       = 1
            JOB_CLOSE_FAILED      = 2
            JOB_SUBMIT_FAILED     = 3
            WRONG_PARAMETERS      = 4
            JOB_DOES_NOT_EXIST    = 5
            WRONG_STARTTIME_GIVEN = 6
            JOB_NOT_RELEASED      = 7
            WRONG_VARIANT         = 8
            NO_AUTHORITY          = 9
            DIALOG_CANCELLED      = 10
            JOB_ALREADY_EXISTS    = 11
            PERIODIC_NOT_ALLOWED = 12
            ERROR_NUMBER_GET_NEXT = 13
            OTHERS                = 14.
IF SY-SUBRC EQ 0.
    WRITE: / 'Direct input job'(022), TBICU-JOBNAME, 'started'.
ELSE.
    WRITE: / 'Direct input failed with return code'(023), SY-SUBRC.
ENDIF.
FORM 0020_DS_NAME.
CALL FUNCTION 'FILE_GET_NAME'
       EXPORTING
            CLIENT           = SY-MANDT
            LOGICAL_FILENAME = PARMS-LDS_NAME
            OPERATING_SYSTEM = SY-OPSYS
       IMPORTING
            FILE_NAME        = PARMS-DS_NAME
       EXCEPTIONS
            FILE_NOT_FOUND   = 1
            OTHERS           = 2.
IF SY-SUBRC NE 0.
    MESSAGE E002 WITH PARMS-LDS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 0030_OPEN_FILE                                           *
      Open physical file for output                                 *
FORM 0030_OPEN_FILE.
OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE. "thg191105
OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE
                                 encoding default. "thg191105
IF SY-SUBRC NE 0.
    MESSAGE E003 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 1000_GET_SOURCE_DATA                                     *
      Read source data into internal table                          *
--> INP_DATA   " Name of internal table passed as parameter       *
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
--> I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
*&      Form 2100_WS_DOWNLOAD
      text                                                           *
--> p1        text
<-- p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.
DATA: FILENAME LIKE RLGRAP-FILENAME.   "SRY28NOV05
DATA: W_FILENAME TYPE STRING.             "SRY28NOV05
DATA: W_FTYP(10) TYPE C VALUE 'DAT'.      "SRY28NOV05
MOVE PARMS-DS_NAME TO FILENAME.       "SRY28NOV05
MOVE PARMS-DS_NAME TO W_FILENAME.      "SRY28NOV05
*BEGIN OF BLOCK COMMENT BY SRY28NOV05
CALL FUNCTION 'WS_DOWNLOAD'
      EXPORTING
        BIN_FILESIZE        = ' '
        CODEPAGE            = ' '
           FILENAME            = FILENAME
           FILETYPE            = 'DAT'
        MODE                = ' '
        WK1_N_FORMAT        = ' '
        WK1_N_SIZE          = ' '
        WK1_T_FORMAT        = ' '
        WK1_T_SIZE          = ' '
        COL_SELECT          = ' '
        COL_SELECTMASK      = ' '
   importing
        filelength          =
      TABLES
           DATA_TAB            = INP_DATA
        FIELDNAMES          =
      EXCEPTIONS
           FILE_OPEN_ERROR     = 1
           FILE_WRITE_ERROR    = 2
           INVALID_FILESIZE    = 3
           INVALID_TABLE_WIDTH = 4
           INVALID_TYPE        = 5
           NO_BATCH            = 6
           UNKNOWN_ERROR       = 7
           OTHERS              = 8.
*END OF BLOCK COMMENT BY SRY28NOV05
*BEGIN OF BLOCK ADDED BY SRY28NOV05
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME                        = W_FILENAME
      FILETYPE                        = W_FTYP
    TABLES
      DATA_TAB                        = INP_DATA
   EXCEPTIONS
     FILE_WRITE_ERROR                = 1
     NO_BATCH                        = 2
     GUI_REFUSE_FILETRANSFER         = 3
     INVALID_TYPE                    = 4
     NO_AUTHORITY                    = 5
     UNKNOWN_ERROR                   = 6
     HEADER_NOT_ALLOWED              = 7
     SEPARATOR_NOT_ALLOWED           = 8
     FILESIZE_NOT_ALLOWED            = 9
     HEADER_TOO_LONG                 = 10
     DP_ERROR_CREATE                 = 11
     DP_ERROR_SEND                   = 12
     DP_ERROR_WRITE                  = 13
     UNKNOWN_DP_ERROR                = 14
     ACCESS_DENIED                   = 15
     DP_OUT_OF_MEMORY                = 16
     DISK_FULL                       = 17
     DP_TIMEOUT                      = 18
     FILE_NOT_FOUND                  = 19
     DATAPROVIDER_EXCEPTION          = 20
     CONTROL_FLUSH_ERROR             = 21
     OTHERS                          = 22.
IF SY-SUBRC NE 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*END OF BLOCK ADDED BY SRY28NOV05
ENDFORM.                               " 2100_WS_DOWNLOAD
*eject
      FORM 4000_PROGRESS_INDICATOR                                  *
      Write progress text to status bar                             *
--> TEXT   " Text passed as parameter                             *
FORM 4000_PROGRESS_INDICATOR USING TEXT.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
       EXPORTING
            PERCENTAGE = 0
            TEXT       = TEXT
       EXCEPTIONS
            OTHERS     = 1.
ENDFORM.
*eject.
      FORM 9000_END_OF_JOB                                          *
      Close files on UNIX                                           *
FORM 9000_END_OF_JOB.
CLOSE DATASET PARMS-DS_NAME.
ENDFORM.
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
--> I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
*&      Form 2100_WS_DOWNLOAD
      text                                                           *
--> p1        text
<-- p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.

Hi,
Thnaks for your reply, This is my requirement.
Here my problem is i am trying to upload the data from flatfile which contain materil number, denominator, Actual UOM, Nominator field values.
Which is the data i need to upload into MM02 and MM01, if material number is new then it has to create the material, if material is already existing it has to update the UOM values.
here i am getting data into my internal table INP_DATA, from that i am trying to upload the data to database by using job name MRP_MATERIAL_MASTER_DATA_UPLOAD with direct input program RMDATIND.
when i execute my program i am getting success message all the records writtin from flatfile to application server. and job started message.
then if i go into sm37 screen there i execute the job it is also giving active message. if i refresh it it is showing job completed message.
then i look at job log status. there i found that for existing material it is expecting material type, for new material it is giving some gravity error.
So could u help me in this it will be gr8.
Thanks & Regards,
RamNV

Issue with data while uploading data form cube 0COOM_C02

Similar Messages

Maybe you are looking for