Table /dvsrepro/sepdol not present in ECC 6.0

Hi,
We are planning an upgrade from 4.6C to ECC 6.0. However while doing a preliminary study of ECC 6.0, we find that table /dvsrepro/sepdol, which is present in 4.6C is not present in ECC 6.0. We are using this table to print the output of batch jobs.
Request inputs on which is the table in ECC 6.0 that has replaced the above mentioned table, which can be used similarly?
Thanks in advance.
Mick

Thanks Max for the prompt response.
Not sure that I have understood what you meant by checking its component? Do you mean that we should check whether it is part of SAP's Aerospace and Defense (A&D) solution? Also how can we check the tables component?
Regards,
Mick

Similar Messages

  • The table tablename is not present in this descriptor.

    Hello, I'm using JDev & TopLink 9.0.3. I get the following descriptor errors. I'm not sure what they mean or how to resolve it. I re-mapped the Advisor descriptor, but with same results. Thanks.
    EXCEPTION [TOPLINK-93] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DescriptorException
    EXCEPTION DESCRIPTION: The table [advsr_demographics] is not present in this descriptor.
    DESCRIPTOR: Descriptor(com.diyh.model.javabeans.Advisor --> [DatabaseTable(party), DatabaseTable(advisor)])
    EXCEPTION [TOPLINK-41] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DescriptorException
    EXCEPTION DESCRIPTION: A non-read-only mapping must be defined for the sequence number field.
    DESCRIPTOR: Descriptor(com.diyh.model.javabeans.Advisor --> [DatabaseTable(party), DatabaseTable(advisor)])

    I figured it out. My Table Reference in the parent descriptor was reversed. I removed it and created another reference with the source from the parent descriptor and the target from the child descriptor.

  • Table M_VMVLB does not exist in ECC 5.0

    Hi,
    We found that table M_VMVLB is available in 4.6C system but not available in ECC 5.0.
    Do yo have ay idea about this? Is there any other table created for this ?
    Regards,
    Umesh

    Hi Umesh,
    as such kind of match code tables like M_VMVLB are not longer supported by the ABAP basis, all these match code tables where replaced by normal data base tables, e.g. the content of M_VMVLB can be found in table SHP_IDX_PICK now.
    General information about the changes in match codes of delivery processing can be found at the release info for 4.70 - component LE-SHP-DL.
    Regards; Ulrich

  • Adding new attribute to Master data - Not present in ECC

    Hi,
    We want to add a new field in the master data object 0plant. the new field is not present in the R/3 side. So we are planning to maintain it manually.
    Is it feasible? Can someone explain how to approach the situation?
    Since it is not going to come in Process chain or any of the mappings below InfoObject will the process chains work properly?
    Regards

    Hi
    if you cant impliment any logic you cam maintani it mannually.
    First add attribute to master data object and activate.
    Do master data load if required.
    Then right click on materdata addtribute and manage -> content tab -> Content
    display complete data and you can maintain attribute values individually for all ercords one by one (will be pain even for 100 records).
    another alternative is of doing file upload for this attribute.
    Regards
    Sudeep

  • How can i display blank table if data not present

    hi all,
    i have problem here.
    i need to display one blank table if there is no data. in default, it just show column name box.
    now i need to add blank box under column name.
    please if you have any advice, let me know.
    regards,
    dityo

    hi,
    the solution that i get is create two similar table with if condition.
    if condition for table A : <?if:count(G_PARTS) > 0?> . G_PARTS is name of group. table A will showed if data present.
    if condition for table B (blank table) : <?if:count(G_PARTS) = 0?>. this blank table will showed if no data.
    if
    table A
    end if
    if
    table B
    enf if
    hope this help.
    rgrds,
    tyo

  • LDAP Userid not present in Backend System

    We are trying to implement a scenario where the user are present in LDAP but are not present in the backend system "ECC".
    Case Scenario: User log into portal using "testid" and want to access the BSP view which pull up the information from the backend system. Now this "testid" is not present in ecc system so i am looking for solution to achieve this scenario where "testid" will be able to pull the information without being created in ECC system.
    This is required for our external customer which we donot want to setup in ecc system.
    Any suggestion or if some one has implemented this scenario and can share how they did it will be really appreciated

    Hi,
    1.) Licensing. Noteably the first aspect that would come from SAP themselves will be licensing. You still need to be transparent about licensing with SAP in your scenario.
    2.) Traceability. If any breaches are made or if any issues occur in yoru backend system, you will need to determine the exact time and it may be that the issue was invoked by several users acting on the system at the same time.
    3.) Locking/Synch and Session Terminations. If mulitple users (using the same backend ID) perform update tasks on the database you may find that they will incur locking issues from trying to update the same record. Synchronous jobs may also result in issues similarly when invoked by different users on the same ID. Session management on the backend systems (dependant on the application) may also result in situations where multiple users may be limited to the max number of concurrent connections under their ID or sessions be "locked" as a result of terminations on the client side - which would require to be cleaned up from time to time.
    While the above are some of the aspects that can be encountered, SAP generally handles these situations rather well, yet from a system managnment perspective you will encounter them from time to time.
    PS: Depending on how you map users - individual mapping can become cumbersome particularly if mappings need to change etc. You can also map at a group level. This will make your life easy particularly say for vendors who have several employees yet need to map to one ECC ID to transact - just create a group per vendor assign the users to the group and map the group to the ID.
    You can also us mass upload to map users efficiently - see:
    http://help.sap.com/saphelp_nw72/helpdata/en/48/a96f43db653206e10000000a42189c/frameset.htm
    https://cw.sdn.sap.com/cw/docs/DOC-107900
    example:
    [User]
    uid=user0002
    Last_Name=Johnson
    $usermapping$:BCE:user=ext_user0002
    $usermapping$:BCE:mappedpassword=initial1

  • In which table Fieled name - IMPORTEDFLAG  is present in ECC 6.0

    Hi,
    Fieled name - IMPORTEDFLAG is present structure  ESTDH  in system 4.6.c
    but in ecc 6.0 this field is not present in structure ESTDH
    so please tell me in which table this field is present

    Hi,
    To check the table name referring field IMPORTEDFLAG,
    Go to SE84 -> Data Dictionary -> Fields -> Table Fields
    Mention the name of the field in Fieldname parameter and execute.
    Regards,
    Ni3.

  • Getting "JTA transaction is not present" error while updating db table.

    Hi All,
    In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
    There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
    OPMN logs:
    <2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Thanks in advance.

    I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
    Is this happening for all BPEL instances or some of them get thru succesfully ?
    Are you EVER updating that particular row of your table ( before/after) ?
    -Shishir

  • How to compare 2 different database to get table name which are not present in second database

    How to compare 2 different database to get table name which are not present in second database

    Sorry cannot test it right now
    use db1
    go
    select * from sys.tables t where not exists
    (select * from db2.sys.tables s where t.object_id=s.object_id)
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • /CCEE/FISISTGRD table is not present

    hi,
    All the CCEE tables are present in my system except FISISTGRD.
    But we want to make use of this table in the program..Can you please help..

    one of the thread says table is
    /CCEE/FISISTGRD Reasons for Reversal enabling to change
    it's not present in std ECC6 too. must be part of some add on package or industry solution.
    https://forums.sdn.sap.com/click.jspa?searchID=25291193&messageID=7046743

  • Comparing two internal tables and deleting the record not present in second

    Hi All,
    I have a internal table itaba with PERNR as primary key and various other columns (1000 records) and table B with PERNR as primary key and 800 records.
    Now what is the best way to compare these two and delete the record from table A when its corresponding record is not present in table B?
    Thanks and Regards,
    Mohan

    HI SIR
    u trained us in accenture
    Hi all
    when ever m running this session in SM35 , M getting error as :
    "LEAVE TO TRANSACTION" MARA-BISMT is not allow
    in batch input
    REPORT YASEC_BDC_NIK_SESSION
    no standard page heading
    message-id zmm
    line-count 65
    line-size 150.
    tables : mara.
    *Top includr program
    INCLUDE YNEW_MAIN_TOP.
    *include yasec_bdc_nik_session_top.
    ***********selection screen *******************
    selection-screen begin of block b1 with frame title text-001.
    selection-screen skip.
    PARAMETERS: p_ifile(128) TYPE c .
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
    PARAMETERS: rad1 TYPE c RADIOBUTTON GROUP 1 USER-COMMAND gr1,
    rad2 TYPE c RADIOBUTTON GROUP 1 .
    SELECTION-SCREEN SKIP.
    PARAMETERS: p_sess TYPE c.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK b1.
    Subroutine call***************************
    INCLUDE YNEW_MAIN_F01.
    *include yasec_bdc_nik_session_f01.
    *********At selection event triggered *************
    at selection-screen on value-request for p_ifile.
    To get F4 help for the input file path
    PERFORM f_f4_input_file.
    AT SELECTION-SCREEN ON p_ifile.
    To validate and upload the input file
    PERFORM f_load_file.
    AT SELECTION-SCREEN ON p_sess.
    To validate the Number of Sessions field
    IF rad2 IS NOT INITIAL AND sy-ucomm EQ c_onli.
    PERFORM f_check_sessions.
    ENDIF.
    ***********Start of selection *******************
    start-of-selection.
    *To process BDC
    PERFORM f_process_bdc.
    TOP OF PAGE
    TOP-OF-PAGE.
    Writes the report heading and for displaying line number.
    PERFORM f_report_header.
    TYPES : BEGIN OF t_final,
    matnr(50) TYPE c,
    bismt(18) type c,
    end of t_final.
    TYPES: BEGIN OF t_fdata,
    data(256) TYPE c,
    END OF t_fdata.
    TYPES: BEGIN OF t_error,
    message(100) TYPE c,
    END OF t_error.
    *Internal table declarations
    *Internal table to load the data from the file that is changed throgh BDC
    DATA : i_final TYPE STANDARD TABLE OF t_final,
    wa_final TYPE t_final.
    *Internal table to store the error messages
    DATA : i_error TYPE STANDARD TABLE OF t_error,
    wa_error TYPE t_error.
    *Internal table to load the raw data
    DATA : i_fdata TYPE STANDARD TABLE OF t_fdata,
    wa_fdata TYPE t_fdata.
    *Internal table to store records of BDC
    DATA : i_bdcdata TYPE STANDARD TABLE OF bdcdata INITIAL SIZE 0,
    wa_bdcdata TYPE bdcdata.
    Internal table to store BDC messages
    DATA: i_bdcmsgcoll TYPE STANDARD TABLE OF bdcmsgcoll INITIAL SIZE 0,
    wa_bdcmsgcoll TYPE bdcmsgcoll.
    VARIABLE DECLARATIONS
    DATA: v_ifile TYPE string,
    v_input TYPE i,
    c_delimiter TYPE c VALUE 'X',
    v_mode TYPE c VALUE 'A',
    v_sessions TYPE i.
    CONSTANTS
    CONSTANTS : c_flagx TYPE c VALUE 'X',
    c_slash TYPE c VALUE '/',
    c_onli(4) TYPE c VALUE 'ONLI',
    c_vl02(4) TYPE c VALUE 'VL02',
    c_s TYPE c VALUE 'A'.
    FORM f_f4_input_file .
    CALL FUNCTION 'F4_FILENAME'
    EXPORTING
    program_name = syst-cprog
    dynpro_number = syst-dynnr
    IMPORTING
    file_name = p_ifile.
    ENDFORM. " f_f4_input_file
    *& Form f_load_file
    FORM f_load_file .
    v_ifile = p_ifile.
    CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
    filename = v_ifile
    filetype = 'ASC'
    has_field_separator = 'X'
    TABLES
    data_tab = i_fdata
    EXCEPTIONS
    file_open_error = 1
    file_read_error = 2
    no_batch = 3
    gui_refuse_filetransfer = 4
    invalid_type = 5
    no_authority = 6
    unknown_error = 7
    bad_data_format = 8
    header_not_allowed = 9
    separator_not_allowed = 10
    header_too_long = 11
    unknown_dp_error = 12
    access_denied = 13
    dp_out_of_memory = 14
    disk_full = 15
    dp_timeout = 16
    OTHERS = 17.
    IF sy-subrc <> 0.
    *Text-103-Input file does not exist.
    MESSAGE e000 WITH text-103 .
    ELSEIF NOT i_fdata IS INITIAL.
    DELETE i_fdata WHERE data = space.
    DESCRIBE TABLE i_fdata LINES v_input.
    ENDIF.
    IF v_input EQ 0.
    Text-104 - Input file is empty.
    MESSAGE e000 WITH text-104 .
    ENDIF.
    ENDFORM. " f_load_file
    *& Form f_check_sessions
    FORM f_check_sessions .
    IF p_sess IS INITIAL.
    MESSAGE e000 WITH text-106.
    ELSE.
    v_sessions = v_input DIV p_sess.
    ENDIF.
    ENDFORM. " f_check_sessions
    *& Form f_process_bdc
    text
    FORM f_process_bdc.
    LOOP AT i_fdata INTO wa_fdata.
    SPLIT wa_fdata AT cl_abap_char_utilities=>horizontal_tab
    INTO wa_final-matnr
    wa_final-bismt.
    APPEND wa_final TO i_final.
    CLEAR wa_fdata.
    ENDLOOP.
    IF rad1 = c_flagx.
    PERFORM f_passbdc_vl02.
    ELSEIF rad2 = c_flagx.
    PERFORM f_sessions_vl02.
    ENDIF.
    ENDFORM. "f_process_bdc
    To populate the Screen information
    p_program Program Name
    p_dynpro Screen Number
    FORM bdc_dynpro USING p_program TYPE any
    p_dynpro TYPE any.
    CLEAR wa_bdcdata.
    Populate the BDC structure with the Screen Information.
    Move the Program name PROGRAM
    wa_bdcdata-program = p_program.
    Move the Screen Number DYNPRO
    wa_bdcdata-dynpro = p_dynpro.
    Indicate the beginning of a new screen
    wa_bdcdata-dynbegin = c_flagx.
    APPEND wa_bdcdata TO i_bdcdata.
    ENDFORM. "f_bdc_dynpro
    *& Form f_passbdc_vl02
    text
    FORM f_passbdc_vl02.
    DATA: l_lines_im TYPE i.
    SORT i_final BY matnr ASCENDING.
    CLEAR wa_final.
    LOOP AT i_final INTO wa_final.
    CLEAR: i_bdcmsgcoll[],
    wa_bdcmsgcoll,
    wa_bdcdata.
    CLEAR: i_bdcdata[].
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'RMMG1-MATNR'
    wa_final-matnr.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
    'X'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'MARA-BISMT'.
    perform bdc_field using 'MARA-BISMT'
    wa_final-bismt.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM02'.
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM03'.
    CALL TRANSACTION 'MM02' USING i_bdcdata
    MODE v_mode
    UPDATE c_s
    MESSAGES INTO i_bdcmsgcoll.
    If error occurred in call transaction 'VA02' then stores all
    information of failed records into internal table i_error_im.
    IF sy-subrc NE 0.
    DESCRIBE TABLE i_bdcmsgcoll LINES l_lines_im.
    CLEAR wa_bdcmsgcoll.
    READ TABLE i_bdcmsgcoll INTO wa_bdcmsgcoll INDEX l_lines_im.
    To capture success and error messages in BDC.
    CALL FUNCTION 'FORMAT_MESSAGE' "#EC *
    EXPORTING
    id = wa_bdcmsgcoll-msgid
    lang = wa_bdcmsgcoll-msgspra
    no = wa_bdcmsgcoll-msgnr
    v1 = wa_bdcmsgcoll-msgv1
    v2 = wa_bdcmsgcoll-msgv2
    v3 = wa_bdcmsgcoll-msgv3
    v4 = wa_bdcmsgcoll-msgv4
    IMPORTING
    msg = wa_error-message
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    IF sy-subrc <> 0.
    ENDIF.
    ELSE.
    WRITE: text-111 COLOR 7.
    ENDIF.
    CLEAR: wa_final.
    REFRESH i_bdcdata.
    ENDLOOP.
    ENDFORM. "f_passbdc_va02
    *& Form bdc_field
    text
    -->P_FNAM text
    -->P_FVAL text
    FORM bdc_field USING p_fnam TYPE any
    p_fval TYPE any.
    CLEAR wa_bdcdata.
    Populate the Field Name
    wa_bdcdata-fnam = p_fnam.
    Populate the field value
    wa_bdcdata-fval = p_fval.
    APPEND wa_bdcdata TO i_bdcdata.
    ENDFORM. "f_bdc_field
    *& Form f_sessions_vl02
    text
    FORM f_sessions_vl02 .
    DATA: l_sindex TYPE sy-tabix VALUE 1,
    l_eindex TYPE sy-tabix,
    l_flag TYPE c VALUE space.
    l_eindex = v_input.
    SORT i_final BY matnr ASCENDING.
    DO p_sess TIMES.
    CALL FUNCTION 'BDC_OPEN_GROUP'
    EXPORTING
    client = sy-mandt
    group = 'Y_VL02_NIK'
    user = sy-uname
    keep = c_flagx
    EXCEPTIONS
    client_invalid = 1
    destination_invalid = 2
    group_invalid = 3
    group_is_locked = 4
    holddate_invalid = 5
    internal_error = 6
    queue_error = 7
    running = 8
    system_lock_error = 9
    user_invalid = 10
    OTHERS = 11.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    CLEAR wa_final.
    CLEAR: i_bdcdata[].
    LOOP AT i_final INTO wa_final FROM l_sindex TO l_eindex .
    IF l_flag = v_sessions.
    CLEAR l_flag.
    EXIT.
    ENDIF.
    l_flag = l_flag + 1.
    CLEAR: i_bdcdata[].
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'RMMG1-MATNR'
    wa_final-matnr.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
    'X'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'MARA-BISMT'.
    perform bdc_field using 'MARA-BISMT'
    wa_final-bismt.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM02'.
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM03'.
    l_sindex = l_sindex + 1.
    ENDLOOP.
    CALL FUNCTION 'BDC_CLOSE_GROUP'
    EXCEPTIONS
    not_open = 1
    queue_error = 2
    OTHERS = 3.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    ENDDO.
    ENDFORM. " f_sessions_vl02
    *& Form f_report_header
    FORM f_report_header .
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    ULINE.
    text-201 - Company: Carrier
    text-102- Batch Data Communication.
    text-202 - System: SAP
    WRITE: /1 sy-vline,
    3 text-201,
    50 text-102,
    100 text-202,
    AT sy-linsz sy-vline.
    text-203 - Program:
    text-204 - Date/Time:
    WRITE: /1 sy-vline,
    3 text-203, sy-repid ,
    100 text-204,sy-datum ,c_slash, sy-uzeit,
    AT sy-linsz sy-vline.
    text-205 - User ID:
    text-206 - Page:
    WRITE: /1 sy-vline,
    3 text-205, sy-uname,
    100 text-206, sy-pagno,
    AT sy-linsz sy-vline.
    FORMAT COLOR OFF.
    ULINE.
    ENDFORM. " f_report_header
    FORM bdc_transaction USING tcode.
    CALL FUNCTION 'BDC_INSERT'
    EXPORTING
    tcode = tcode
    TABLES
    dynprotab = i_bdcdata
    EXCEPTIONS
    internal_error = 1
    not_open = 2
    queue_error = 3
    tcode_invalid = 4
    printing_invalid = 5
    posting_invalid = 6
    OTHERS = 7.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ELSE.
    WRITE: / text-109 ,wa_final-matnr,
    text-110 .
    ENDIF.
    ENDFORM. "bdc_transaction

  • Master data not present in the reporting cube

    Dear Experts,
    There is a scenario in report design for me.
    I have already created the Bex report and all the fields as mentioned are in the  sales report.
    Client now wants to include two more fields in the report.
    One is the keyfig  " Net value" which is present in the sales cube  and i have already included in the report
    and another field which is master data  0profit_center  is not present in the cube.
    Any ideas how can i include this  0profit center  data  so that i can display in the report?
    As far as i understand, I need to include this master data in the sales  Infocube which is being used for reporting.
    But i am pondering  upon the impact on the system because of this.
    Now i have checked the BI system and the ECC table. In VBRP table of ECC,  the profit center is present.
    But when i see in BI the profit center is not being loaded  from ECC but from flat file source system.
    So i am confused how to go forward.
    Can anyone suggest me  what should be my approach?
    Best Regards!!

    You didn't understand what we suggested.
    Rather than checking 0profit_ctr master data, you need to find the info objects(which are part of your cube) which have master data. in those 0profit_ctr can be a attribute. if yes then navigation settings will work.
    if not then you can add 0profit_ctr to info cube and user master data look up thru routine or option read from master data(bw 7.3).
    Other wise, directly add 0profit_ctr to your flat file data source(and cube) and maintain data thru flat file.
    To look up your cube and 0pfirt_ctr need to have relations with another info objects other wise not possible.

  • "Table VSEOPARENT is not in the database" after SolMan system copy to x64

    Hi SDNners,
    We've just completed a system copy of our SolMan 3.1 system onto a new
    (Xeon x64 based) server. This system copy is part of the process of
    moving SolMan 3.1 from an old server onto 64bit hardware and then
    upgrading it to SolMan v4 and Oracle 10G.
    Although the system appears to start properly in the MMC, we are unable
    to log into the system through SAPGUI - we get a SYNTAX_ERROR window
    instead of a logon screen.
    I've checked the SysLog from within the MMC and noticed a number of
    errors stating:
    Database: Table VSEOPARENT is not in the database
    Database: Table VSEOIFIMPL is not in the database
    Database: Table VSEOIFCOMP is not in the database
    I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and
    it confirmed that the table didn't exist. I then ran the same command
    on the source SolMan system and it showed that VSEOPARENT DID exist. I
    don't understand how these VSEO* tables could have gone missing between
    the source and target systems.
    I've searched OSS for VSEO* and cannot find anything. Please help!
    Thanks,
    Arwel.

    We have 640 kernel, ECC 5.0 and BASIS patch 23.
    For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.
    It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.
    I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.
    Using migration monitor I did re-export and re-import and this time all views are imported in target.
    Regards,
    Mamadi.

  • CRM To ECC Sold to party Communication Details Not populated in ECC

    Hi All
    i have one problem when we create sales order through crmd_order we need to give sold to party and ship to party numbers suppose like
    8000002166 for both and status i keep as order created and in partner tab i i seem all partner funtions(sold to, ship to ,bill to, payer)with 8000002166
    in header overivew i given posting date as feature date like 30-09-2013 then i try to save this order.
    the order generated sucussfully but problem is i am not getting sold to party details in ECC when i check VA03 And open cretaed order in CRM and clicking on sold to party and i seem details for this but i am not getting communication details like telephone number and email id extension number.
    for this sold to party we already maintained all communication details in CRM.When i open this sold to party BP i am able to see all details
    didnt understand why these details not replicated to ECC?
    We implemented one custom class there we implemented badi.
    IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
    i am not getting BAPI ADDRESS Table values into  CT_BAPIADDR1
    how can i send communciation details to ECC For sold to party?
    The code part we follow like below
    TYPES : BEGIN OF t_otc,                                                        " Type to create a table with the given columns.
              bpid            TYPE bu_partner,                                       " variable of store processed business partner ID's
              otcid           TYPE bu_partner,                                       " variable of store processed OTC ID's
              otcguid         TYPE bu_partner_guid,                                  " variable of store processed OTC GUID's
              address         TYPE bapibus1006_address,
              tel1_numbr      TYPE ad_tlnmbr1,
              tel1_ext        TYPE ad_tlxtns1,
              e_mail          TYPE ad_smtpadr,
              END OF t_otc.
    *&                             V A R I A B L E S                         &*
      DATA : lv_bp_payer      TYPE bu_partner,                                       " Variable To Cast the payer Id into BU_Partner data type.
             lv_partner_fct   TYPE crmt_partner_fct,                                 " Variable To Store Partner Function Number.
             lv_partner       TYPE bu_partner,                                       " Variable To Store Current Business Partner ID.
             lv_process_type  TYPE crmt_process_type,                                " Variable to Store process type.
             lv_sales_org     TYPE crmt_sales_org,                                   " Variable to store sales org. name of order
             lv_dis_channel   TYPE crmt_distribution_channel,                        " Variable to store distribution channel of order.
             lv_division      TYPE crmt_division,                                    " Variable to store division of sales org. data.
             lv_role          TYPE comt_partner_parvw,                               " Variable to store retrieved role from FM.
             lv_role_value    TYPE parvw,                                            " Variable to store the role value of Partner Functions.
             lv_otc_guid      TYPE bu_partner_guid,                                  " Variable to store OTC GUIDs for the OTC ID.
             lv_otc_id        TYPE kunnr.                                            " Varaible to OTC ID revocered from Table.
      DATA: lv_busspartner           TYPE bapibus1006_head-bpartner,
            lw_central_data          TYPE bapibus1006_central,
            lw_centraldata_person    TYPE bapibus1006_central_person.
    *&                             W O R K A R E A S                         &*
      DATA : lw_address       TYPE bapibus1006_address,                              " Work Area to store address recovered for BPID.
    *Start of code change for Defect 904 Fix
             lw_tel           TYPE bapiadtel,
             lw_email         TYPE bapiadsmtp.
    *End of code change for Defect 904 Fix
    *&                          INTERNAL TABLES                              &*
      DATA : li_otc           TYPE TABLE OF t_otc,                                   " Internal Table to Store the OTC IDs and BPS.
             li_values        TYPE          zconst_values_t,
    *Start of code change for Defect 904 Fix
             li_tel           TYPE STANDARD TABLE OF bapiadtel,
             li_email         TYPE STANDARD TABLE OF bapiadsmtp.
    *End of code change for Defect 904 Fix
    *                       F I E L D - S Y M B O L S                         *
      FIELD-SYMBOLS: <f_orderadm>      TYPE bad_orderadm_h_mess,
                     <f_otc>           TYPE t_otc,                                   " Field-Symbol to Read the OTC TABLE data.
                     <f_partner>       TYPE bad_partner_mess,                        " Field-Symbol of Partner Table For Looping.
                     <f_bapiparnr3>    TYPE bapiparnr3,                              " Field-Symbol to Store The Row of BAPIPARNR3.
                     <f_bapiaddr1>     TYPE bapiaddr1,
                     <f_orgman>        TYPE bad_orgman_mess,                         " Field-Symbol to Read the ORGMAN table.
                     <f_values>        TYPE zcr_const_values.
    *&                             C O N S T A N T S                         &*
      CONSTANTS :  lc_program_name     TYPE progname      VALUE 'ZOTC',
                   lc_param_payer      TYPE paramname     VALUE 'PAYER',              " Constant to Store Payer Parameter name.
                   lc_ref_kind         TYPE crmt_object_kind VALUE 'A',
                   lc_req_1            TYPE zrequest_no VALUE '1',
                   lc_req_2            TYPE zrequest_no VALUE '2'.
    * Retrieving the general and Common Data for a Order.
      READ TABLE it_bus_trans_msg-orderadm_h INDEX 1 ASSIGNING <f_orderadm>.
      IF sy-subrc EQ 0.
        lv_process_type = <f_orderadm>-process_type.
      ENDIF.
    * Reading the Orgnisation Details from ORGMAN Table.
      READ TABLE it_bus_trans_msg-orgman WITH KEY ref_kind = lc_ref_kind ASSIGNING <f_orgman>.
      IF sy-subrc EQ 0.
    *   Storing the Sales Organisational Data to find the OTC_ID.
        lv_sales_org = <f_orgman>-sales_org.
        lv_dis_channel = <f_orgman>-dis_channel.
        lv_division = <f_orgman>-division.
      ENDIF.
    * Retrieving the partner function number for the payer by giving requirement no 2 and rule no 1.
      CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
        EXPORTING
          pi_program_name = lc_program_name
          pi_req_no       = lc_req_2
        IMPORTING
          po_const_values = li_values.
      IF sy-subrc <> 0.
        RETURN.
      ENDIF.
    * Reading the value for the constant with the name as PAYER.
      READ TABLE li_values WITH KEY param_name = lc_param_payer ASSIGNING <f_values>.
      IF sy-subrc NE 0.
        RETURN.
      ENDIF.
    * Retrieving the Partner ID for the PAYER.
      READ TABLE it_bus_trans_msg-partner ASSIGNING <f_partner> WITH KEY ref_partner_fct = <f_values>-constant_value.
      IF sy-subrc EQ 0.
    *   Storing the current partner ID.
        lv_bp_payer = <f_partner>-ref_partner_no.
      ENDIF.
      REFRESH li_values.
    * Retrieving the Partner Function Number which are to be checked for replacing with the OTC ID with request no 1 and rule no 01.
      CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
        EXPORTING
          pi_program_name = lc_program_name
          pi_req_no       = lc_req_1
        IMPORTING
          po_const_values = li_values.
      IF sy-subrc <> 0.
        RETURN.
      ENDIF.
    * Transferring the constant value to our table for Partner Fucntion.
      LOOP AT li_values ASSIGNING <f_values>.
    * Read Partner table for Header data and the reference partner function retrieved.
        READ TABLE it_bus_trans_msg-partner WITH KEY ref_kind = lc_ref_kind ref_partner_fct = <f_values>-constant_value ASSIGNING <f_partner>.
        IF sy-subrc EQ 0.
    *     Storing Current Partner Function.
          lv_partner_fct = <f_partner>-ref_partner_fct.
    *     Storing Current Partner No.
          lv_partner = <f_partner>-ref_partner_no.
    *     Retrieving the Partner Role (R/3) for the current partner function of CRM.
          CALL FUNCTION

    The problem is in the Lotus Notes security level, not in SAP.

  • G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

    i am getting the dump.
    the fuction module is not presend in ECC 5.0
    Runtime Errors         CALL_FUNCTION_NOT_FOUND                                                     
    Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC                                                 
    Date and Time          04/05/2007 07:13:25                                                         
    ShrtText                                                                               
    Function module "G_G_IDOC_REC_ZZINCOT" not found.                                             
    What happened?                                                                               
    The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be                          
        found in the Function Library.                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLGUIF" had to be terminated because one of the                   
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                         
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that caused the                                      
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer                      
         termination messages, especially those beyond their normal deletion                          
        date.                                                                               
    is especially useful if you want to keep a particular message.                                
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                      
        . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',                
         was neither                                                                               
    caught nor passed along using a RAISING clause, in the procedure                              
         "IDOC_INPUT_GLROLL" "(FUNCTION)"                                                             
    Since the caller of the procedure could not have expected this exception                      
         to occur, the running program was terminated.                                                
        The reason for the exception is:                                                              
        The program "SAPLGUIF" contains a CALL FUNCTION statement. The name                           
        of the function module to be called is "G_G_IDOC_REC_ZZINCOT".                                                                               
    No function module exists with the name "G_G_IDOC_REC_ZZINCOT".                               
        All function modules are stored in the Function Library (SE37).                                                                               
    Possible reasons:                                                                               
    a) Wrong name specified. Particular attention should be paid                                  
           to upper/lower case and underscores ("_")                                                  
        b) Transport error                                                                               
    c) If an enqueue/dequeue module has been used, the lock object                                
           may not have been activated (ABAP Dictionary)                                              
           may not have been activated (ABAP Dictionary).                                             
    How to correct the error                                                                               
    Check the last transports to the R/3 System.                                                  
        Is the program "SAPLGUIF" currently being changed?                                            
        If an enqueue/dequeue module is involved, is the activation                                   
        of the lock object missing in the ABAP/4 Dictionary?                                                                               
    You may able to find an interim solution to the problem                                       
        in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC                                        
        "SAPLGUIF" or "LGUIFU05"                                                                      
        "IDOC_INPUT_GLROLL"                                                                               
    Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":                                                                               
    G_G_IDOC_REC_COFIT                                                                               
    G_G_IDOC_REC_FILCT                                                                               
    G_G_IDOC_REC_ECMCT                                                                               
    G_G_IDOC_REC_GLPCT                                                                               
    G_G_IDOC_REC_GLT0                                                                               
    G_G_IDOC_REC_SECURE                                                                               
    G_POSTING_ZZINCOT                                                                               
    G_G_IDOC_SEND_COFIT                                                                               
    G_G_IDOC_SEND_ECMCT                                                                               
    G_G_IDOC_SEND_SECURE                                                                               
    If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
        The exception must either be prevented, caught within the procedure                           
         "IDOC_INPUT_GLROLL"                                                                               
    "(FUNCTION)", or declared in the procedure's RAISING clause.                                  
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "d48ix100"                                                          
        Network address.......... "151.162.153.62"                                                    
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "00C65EFD4C00"                                                      
        Character length......... 8 Bits                                                              
        Pointer length........... 64 Bits                                                             
        Work process number...... 2                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "d48ix100"                                                          
        Database type............ "ORACLE"                                                            
        Database name............ "D48"                                                               
        Database owner........... "SAPR3"                                                                               
    Character set............ "en_US.ISO8859-1"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Nov 5 2006 20:46:58"                                               
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "156"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16128                                                               
        EM....................... 8379856                                                             
        Heap..................... 0                                                                   
        Page..................... 16384                                                               
        MM Used.................. 2530176                                                             
        MM Free.................. 1657232                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 010                                                                      
        User................ "OS0730"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "YICUPLD "                                                               
        Program............. "SAPLGUIF"                                                               
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".               
        The main program was "Y21091IRECON ".                                                                               
    The termination occurred in line 65 of the source code of the (Include)                       
         program "LGUIFU05"                                                                               
    of the source code of program "LGUIFU05" (when calling the editor 650).                       
        Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"                 
         occurred in the                                                                               
    procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not                   
         declared in the                                                                               
    RAISING clause of the procedure.                                                              
        The procedure is in the program "SAPLGUIF ". Its source code starts in line 5                 
        of the (Include) program "LGUIF$05 ".                                                         
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    35                                                                               
    36 *Prüfen, ob Customizing richtig eingestellt ist                                             
       37     CHECK EXIT IS INITIAL.                                                                  
       38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.                                            
       39                                                                               
    40 *Für Einzelposten neue Belegnummern vergeben                                                
       41     CHECK EXIT IS INITIAL.                                                                  
       42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER                                           
       43                                       IDOC_CONTRL-MESTYP.                                   
       44                                                                               
    45 *Füllen der Segmentdaten                                                                    
       46     CHECK EXIT IS INITIAL.                                                                  
       47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.                                               
       48                                                                               
    49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.                                          
       50       IDOC_SEGMENT = IDOC_DATA.                                                             
       51       APPEND IDOC_SEGMENT.                                                                  
       52     ENDLOOP.                                                                               
    53                                                                               
    54 *Name des zu rufenden Funktionsbausteines ermitteln                                         
       55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.                                                        
       56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.                              
       57                                                                               
    58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen                                        
       59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB                                     
       60     IF NOT E1GLTTF-TAB30 IS INITIAL.                                                        
       61       L_TAB30 = E1GLTTF-TAB30.                                                              
       62     ELSE.                                                                               
    63       L_TAB30 = E1GLTTF-TAB.                                                                
       64     ENDIF.                                                                               
    >>>>>     CALL FUNCTION ROL_FUNCNAME                                                              
       66          EXPORTING                                                                          
       67               MESTYP             = IDOC_CONTRL-MESTYP                                       
       68               DOCNUM             = IDOC_NUMBER                                              
       69               TAB                = L_TAB30                                                  
       70          TABLES                                                                               
    71               IDOC_SEGMENT       = IDOC_SEGMENT                                             
       72               IDOC_STATUS        = IDOC_STATUS                                              
       73               RETURN_VARIABLES   = RETURN_VARIABLES.                                        
       74                                                                               
    75   ENDLOOP.                                                                               
    76                                                                               
    77 *Keine IDOC's empfangen                                                                     
       78   IF SY-SUBRC NE 0.                                                                         
       79     RAISE WF_ERROR_PROCESS.                                                                 
       80   ELSE.                                                                               
    81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind                          
       82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'                                                   
       83                            OR MSGTY = 'E'.                                                  
       84       EXIT.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 2                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 0                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                           &

    I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
    If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

Maybe you are looking for