SDL, transport and business sytem groups

HI,
i have test and qulity sap systems:
BSD, XIT (test) and BSQ, XIQ (qulity)
and also have 1 third party system, that is test and quality system at once. (HTTPCLIENT)
i've created business system HTTPCLIENT at test business system group. how can i use the same HTTPCLIENT system as quality system group (or target system).

Hi,
Check these
Create Transport Groups and Transport Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Transport TS and BS From SLD
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Regards
Seshagiri

Similar Messages

  • Business Partner Role  and Business Partner Grouping

    Hello Everybody!
    Business Partner Role  and Business Partner Grouping.
    Which correlation ist between this attributes existing.
    In which table are this infos stored, In order create I can use
    e.g. BUPA_CREATE_FROM_DATA
    but how is the way inversely. Suppose I want to abtain the information
    about a existing business partner which group he has etc.
    Regards
    sas

    Dear Sas,
    Business Partner Grouping is used to determine the number ranges to be used by the business partner at the time of creation.
    Business Partner Role determines the subset of all the data available to be shown and edited.
    I will give you a very simple (but imaginary) example for understanding the role concept: the business partner in a role of employee might allow you to enter a department id. So this field should be available to you for input when you edit the business partner in the role of employee. But suppose the same business partner is also a person who is your customer. And your customer will require a default payment term. So this field should be available for input when you edit the business partner in the role of a customer. Also, some applications use these roles to determine if the business partner is suitable for particular transaction. In the above example, Payroll application will only allow those Business Partner to be used if they are maintained as an employee. Similarly the sales application can mandate that you can only sell a product to a business partner if he is maintain in a 'customer' role.
    Please understand the example above is not real but given for the understanding of the concept of role.
    You can use the function module 'BUPA_CENTRAL_GET_DETAIL' to find the business partner group. And you can use the function 'BUPA_ROLES_GET' to find the role assigned to a Business Partner.
    Regards, Rakesh

  • Account group and Business partner link

    Hi all,
    Is there any relation maintained for Account group (From R/3)  and Business Partner Role in GTS system?

    Hi Balu,
    In GTS, system does not consider the Account group while creating a BP role for a BP whereas it only considers the classification of Vendors or Customers. If a Customer master is created in R/3 irrespective of Account Group, BP role SLLCPC will be assigned whereas if a Vendor is created in R/3, then BP role SLLCPS will be assigned.
    Hope this answers the query.
    Regards,
    Shiva Shankar

  • Number group nt maintained for CC 1000 section 1200 and Business Place

    Dear All
    Experts.
    Hi,
    We are facing an error while performing J1INCHLN. At the time of posting outgoing payemnt
    through F-07 we are getting following error.
    " Number group not maintained for CO code 1000 section code 1200 and Business Place 194C."
    However we have maintained the the section code and number range for respective section
    codes i.e. 1200 & 1300 as number range group 02.
    Still facing the same problem.
    Please help on this.
    Regards,
    Sharvari Joshi.

    Dear,
    Sometimes number range groups have been maintained but not the proper tables. Check table J_1IEWTNUMGR_1 in SE16 if number range gorups have been maintained, if not then maintain this table using SM30 or SE16.
    Regards,
    Chintan Joshi

  • Number group not maintained for CO code 1424 section IEQ1424 and business p

    while create remittance challan....  this error accured Number group not maintained for CO code 1424 section IEQ1424 and business place 194C...     using T- code: J1INCHLN

    Hi,
    Number Group and Number range not maintained for the  Business Place /Off. w/Tax Key in T.code J1INUM or In this Path  : SPRO Financial Accounting (New)-Withholding Tax-Withholding Tax-Posting-Posting-Remittance Challans-Remittance Challans -Excute and Maintain the Number Group and also for the Number Group ,Manain the Number Range in J1INO T.code 
    Once you do the above customization, the Mentioned Error will be cleared.
    Thanks
    Goutam

  • Number group not maintained for CO code RIL section IEQRIL and business pla

    Hi all,
    I get an errror at the time of creation of TDS challan
    "Number group not maintained for CO code RIL section IEQRIL and business place 194H"
    Regards
    Amit

    Hi narayana
    Thanks for ur reply. Is it requires to create entries manually in this table cant it be directly directed to this table from any other area from where the entries will be directly go to this table
    Regards
    Amit

  • Number group not maintained for CO code 1000 section IEQ1000 and business p

    Hi SAP gurus,
    while i am trying to create the remittance challan in the easy access screen with the tt.code J1INCHLN an error message is coming like "Number group not maintained for CO code 1000 section IEQ1000 and business place 194C". Can anybody suggest me how to solve this. Points will be assigned
    Regards
    Curtis

    Hi,
    Check the following information once again...
    Use the following path:
    SAP Customizing Implementation Guide >> Financial Accounting>> Financial Accounting Global Settings >> Withholding Tax >> Extended Withholding Tax >> Postings>> India >> Remittance Challans >>
    Maintain Number Groups
    Assign Number Ranges to Number Groups
    Maintain Number Ranges
    1.Maintain number groups
    co.code Sec.code official w.h.tax key no.group
    1000 1000 194c 01
    2.Assign Number Ranges to Number Groups
    Number group Int nr
    EX: 01 01
    3.Maintain Number Ranges
    click on change intervals
    enter the relevant company code
    ex:
    Year From number to number current number EXT ...
    2008 1000000 1999999
    Check with previious no.ranges, if this is the first time use the new number range or existing number range
    It will resolve ur issue.
    all the best

  • Number group not maintained for CO code section  and business place

    Hi Experts,
    I am Facing this error 'Number group not maintained for CO code section  and business place' while posting TDS entry ,
    I have maintained the number groups for internal challan numbers and i have also checked the table 'J_1IEWTNUMGR_1' , the entry exists, I am not able to track the problem.?
    the below mentioned are the example of the entry which is maintained inspite of which am facing the error.
    company code - 4001
    Business Place 4384
    Section  194I
    Thanks in Advance,

    Dear,
    Please check whether you have maintained entry in SPRO>IMG>Financial Accounting>****>Withholding Tax>Extended Withholding Tax>Posting>Certificate Numbering for Withholding Tax>Numbering Concenpt4 :Assign Numbering Group
    If not then please maintain the same.
    Regards.
    Vivek

  • Number Group Not Maintained for Section IEQIN02 and Business Place 194B

    Hi,
    We have not deducted TDS under 194 B until now but using other sections only like 194 C. Currently there is a deduction under 194 B section and we want to pay through J1INCHLN against this deduction. But we are getting the errror messege "Number Group Not Maintained for CO Code R001 Section IEQIN02 and Business Place 194B"
    Please reply what configuraton needed for this.
    Regards
    Prakash

    Hi,
    Go to SM30 and maintain the values for all the below items with Co.Code, Official Key and Section code
    J_1IEWT_CERT
    J_1IEWT_CERT_N
    J_1IEWT_CERTNO
    J_1IEWTNUM
    J_1IEWTNUMGR
    J_1IEWTNUMGR_1
    J_1IEWTNUMGR_N
    Regards
    Balaji

  • Business Event groups and types.

    Dear Experts
    Following is the case where user is end up with the existing no. range for the Event groups and types.
    How can i assign new no. range for the both?
    Below is the current situation:
                                                    Int                                                      Ext
                                      From         To            Current                      From         To
    Business event type     70002100  70009999
    Course                        71000000  79999999  71001849      
    Location                      70010200  70010399  0      
    Resource                     70010400  70010999  70010424      
    External person            70011000  70019999 0      
    Business event group    70000100  70002099
    Your help will be really appreciated
    Regards
    Jayeeta

    Hi nalla
    thank u so much for your reply
    but what i want to know is that all existing number ranges are exhausted
    how do i now assign new number ranges to the Business Event groups & types
    please help
    Regards
    jayeeta

  • Logical system and business system

    Hi experts, please help me with the below questions---
    1) What is the diff between logical system and business system?
    2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
    3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

    Hi,
    Business System :
    1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
    2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
    Business Service:
    1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
    2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
    3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
    4.Business Service has no SLD Entries and No Assigned Products and SWCV's
    Regards
    Sangeetha

  • Badi and Business event( Urgent)

    Hi experts,
          I am new to badi and business event 1120P. Please post how this business event exactly comes in to picture in this badi. also how to find this business event?
    And also Post the logic or code. The requirement is given below . Pls Post the solution. Its very urgent.
    Enhancement Summary
    Two user exits are needed to determine the correct G/L Account and Cost Center on Shipment Cost documents and post the Material Group on the Accounting document. BADI_SCD_ACCTG and Business Event 1120P can be used to accommodate the new functionality.
    Business Process
    Specific G/L Accounts and Cost Centers have to be determined to post on the Shipment Cost document. This is needed to provide accurate management reporting capabilities on shipments for Sales Order or Stock Transfer Order. A new custom table must be created which contains the following information: Distribution, Mode of Transport, Account, Cost Center Material group. Distribution is an identifier here if this shipment originated from an SO or STO.
    There are no screens involved in this enhancement.
    Components
    Table: ZTABLE1
    Field     Data Element     Type     Length     Description
    MANDT     MANDT     CLNT (key)     3     Client
    DISTRIBUTION     Z_DISTRIBUTION     CHAR (key)     1     Distribution
    MOT     ZZDEF_MOT     CHAR (key)     2     Mode of Transportation
    MATKL     MATKL     CHAR (key)     9     Material group
    SAKNR     SAKNR     CHAR     10     G/L Account Number
    KOSTL     KOSTL     CHAR     10     Cost Center
    This table gets updated manually by the FI team.
    Values for Distribution are:
    ‘1’  =  Primary Distribution to Refinery
    ‘2’ = Primary and Secondary– Excluding refinery
    All entries must be checked against SAP config and master tables
    User exit BADI BADI_SCD_ACCTG will be used to determine the correct G/L Account, Cost Center and Product Group based on Distribution and Mode of Transport. This BADI gets called only when a new Shipment Cost document get created.
    Once the BADI determined the new values it populates field c_vfkn-sakto with the G/L account, field c_vfkn-kostl with the Cost Center and exports the Product group to memory.
    There is no field on the Shipment Cost Document to store the Product group. Therefore another mechanism must be used to get the Product Group on the accounting document.
    Business Event 1120P can be used to import the Product group out of memory and put it on BSEG-MATNR. Structure BSEG_SUBST must be enhanced with field MATNR for this purpose.
    Function, Rules, Exits      Description of Functionality, Rules, Exits
    BADI_SCD_ACCTG     Business Add-In for Shipment Cost Account Assignment
    Business Framework     Business Event 1120P can be used to import the Product Group from memory and to populate field BSEG_SUBST-MATNR.
    This event gets called from different places. It needs to be ensured that it only populates the value when it was called from BADI_SCD_ACCTG.
    Custom Table     A look-up Table needs to be maintained for Distribution, Mode of Transport, G/L Account, Cost Center and Material Group
    Transaction code     To maintain the new table
    Append Structure     To enhance structure BSEG_SUBST with MATNR
          Business Add-In BADI_SCD_ACCTG can be used to determine the account assignments for a shipment cost item to set the G/L Account and Cost Center. All data needed to determine the new information gets provided in this BADI.
    Logic:
    •     Determine if STO or SO based on Document Category from internal table I_REFOBJ-VTRLP field VGTYP If is C then Distribution type is Sales Order (Primary and Secondary – Excluding Refinery – ‘2’ ) else we need to check the receiving plant. If the receiving plant (I_REFOBJ-VTRLK field WERKS) is a refinery the Distribution type is Primary (1) else it’s a (Primary and Secondary – Excluding Refinery – ‘2’ ). Refineries can be identified via Function Module ZPLANTCLASSIFICATION. The plant must be passed into Import Parameter IP_SAPPLANT and field INT_PLANTCHAR-ATNAM must be looked up with value SAPTYPE. If it exists and field ATWRT contains ‘RFY’, the plant is a refinery.
    •     Product Group can be determined from the Material master through Material group field MARA-MATKL.
    •     Mode of Transport will be passed in the BADI in VTRLK-OIC_MOT.
    •     Select single entry from table ZTABLE1based on Distribution, Mode of Transport and Material Group. If nothing gets selected, error message ‘No entry exists in table ZTABLE1for Distribution (distribution), MOT (MOT) & Mat. Group (material group)’ should be triggered.
    •     Move ZTABLE1-SAKNR  to c_vfkn-sakto and ZTABLE1-KOSTL to c_vfkn-kostl
    •     The Material group must be exported to memory in BADI_SCD_ACCTG
    •     The Material group must be imported from memory in Business Event BP1120P
    •     Free Memory in Business Event BP1120P
    This is VI01 – Creation of Freight Cost Item screen
    and also code for function module ZPLANTCLASSIFICATION below
    FUNCTION zplantclassification .
    ""Local interface:
    *"  IMPORTING
    *"     REFERENCE(IP_SAPPLANT) LIKE  AUSP-OBJEK OPTIONAL
    *"     REFERENCE(IP_CPSPLANT) LIKE  AUSP-ATWRT OPTIONAL
    *"     REFERENCE(IP_SISLOC) LIKE  AUSP-ATWRT OPTIONAL
    *"  EXPORTING
    *"     VALUE(EP_SAPPLANT) LIKE  AUSP-OBJEK
    *"     VALUE(EP_CPSPLANT) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SISLOC) LIKE  AUSP-ATWRT
    *"     VALUE(EP_OWNERSHIP) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SMISTYPE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SPOTREF) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SUBTYPE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SUPPLYREGION) LIKE  AUSP-ATWRT
    *"     VALUE(EP_TYPE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_DISTAREA) LIKE  AUSP-ATWRT
    *"     VALUE(EP_GEOGAREA) LIKE  AUSP-ATWRT
    *"     VALUE(EP_HMF) LIKE  AUSP-ATWRT
    *"     VALUE(EP_IATACODE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_IRSTCN) LIKE  AUSP-ATWRT
    *"     VALUE(EP_OPSAREA) LIKE  AUSP-ATWRT
    *"     VALUE(EP_PLANTSTAT) LIKE  AUSP-ATWRT
    *"     VALUE(EP_PORTCODE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_REFAREA) LIKE  AUSP-ATWRT
    *"     VALUE(EP_SAPTYPE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_MFGWARRANTY) LIKE  AUSP-ATWRT
    *"     VALUE(EP_USERTYPE) LIKE  AUSP-ATWRT
    *"     VALUE(EP_TRMCENTER) LIKE  AUSP-ATWRT
    *"     VALUE(EP_TRANSCENTER) LIKE  AUSP-ATWRT
    *"     VALUE(EP_FEIN) LIKE  AUSP-ATWRT
    *"  TABLES
    *"      INT_PLANTCHAR STRUCTURE  ZPLANTCLASSIFICATION OPTIONAL
    *"  EXCEPTIONS
    *"      NO_OBJEK_FOUND
    *"      NO_CPSPLANT_FOUND
    *"      NO_SISLOC_FOUND
    *"      NO_INPUT_FOUND
    *"      VALID_PLANT_NO_CHARACTERISTIC
    *"      ONE_TO_MANY_ISSUE
    *"      PLANT_NOT_FOUND_ZDEF_DELPLANT
    *"      UNKNOWN_ERRORS
    FM Name: ZPLANTCLASSIFICATION     
    Created By  :  SYUB                                                  *
    Description : Function Module to retrieve plant characteristics      *
    The function module has two capabilities:
    1. Retrieve only the necessary characteristics
    2. Retrieve the whole characteristics into an internal table.
    Parameter Description                                                *
    In the future, if there is a new characteristic added to the
    plant classification tables, the characteristic has to be added
    to the list of the export parameters and the loop statement.
      TABLES: ausp, cabn, ksml, zdef_delplant.
      DATA: ws_objek LIKE ausp-objek,
            ws_countchar TYPE i,
            ws_countplant TYPE i.
    *Internal table for SAP plant
      DATA: BEGIN OF int_plant OCCURS 0,
            plant LIKE ausp-objek,
            END OF int_plant.
    *sap plant code is the input parameter.Move objek, atnam, and atwrt to
    *internal table PLANTCHAR using inner join of AUSP, CABN, and KSML to
    *synch up the internal characteristic numbers throughout the 3 tables.
      IF NOT ip_sapplant IS INITIAL.
        SELECT auspobjek cabnatnam ausp~atwrt
          INTO CORRESPONDING FIELDS OF TABLE int_plantchar
          FROM ksml AS ksml
          INNER JOIN cabn AS cabn
            ON cabnatinn = ksmlimerk
          INNER JOIN ausp AS ausp
            ON ausp~objek = ip_sapplant
            AND auspatinn = cabnatinn
            AND ausp~mafid = 'O'
            AND ausp~klart = 'Z01'.
    *Checking the existence of ip_sapplant in the table, if it doesn't
    *exist, raise the exception else if it exists, check if it has
    *characteristic values.
        IF sy-subrc NE 0.
          RAISE no_objek_found.
        ELSE.
          DESCRIBE TABLE int_plantchar LINES ws_countchar.
          IF ws_countchar LT 2.
            RAISE valid_plant_no_characteristic.
          ENDIF.
        ENDIF.
    *cps plant code is the input parameter. Move objek from table AUSP to
    *ws_objek using inner join of CABN and AUSP to match up the internal
    *characteristic numbers from the 2 tables.
      ELSEIF NOT ip_cpsplant IS INITIAL.
        SELECT ausp~objek
          INTO TABLE int_plant
          FROM ausp AS ausp
          INNER JOIN cabn AS cabn
            ON cabn~atnam = 'OLDCODE'
              WHERE auspatinn = cabnatinn
                AND ausp~mafid = 'O'
                AND ausp~klart = 'Z01'
                AND ausp~atwrt = ip_cpsplant.
    *Checking the existence of ip_cpsplant in the table
        IF sy-subrc EQ 0.
    *Counting the number of SAP plants in the internal table int_plant
          DESCRIBE TABLE int_plant LINES ws_countplant.
    *Moving the values of objek, atnam, and atwrt to PLANTCHAR using objek
    *from ws_objek.
          IF ws_countplant EQ 1.
            LOOP AT int_plant.
              SELECT auspobjek cabnatnam ausp~atwrt
                INTO CORRESPONDING FIELDS OF TABLE int_plantchar
                FROM ksml AS ksml
                INNER JOIN cabn AS cabn
                  ON cabnatinn = ksmlimerk
                INNER JOIN ausp AS ausp
                  ON ausp~objek = int_plant-plant
                  AND auspatinn = cabnatinn
                  AND ausp~mafid = 'O'
                  AND ausp~klart = 'Z01'.
            ENDLOOP.
    *If there more than one SAP Plants, then raise an exception.
          ELSEIF ws_countplant GT 1.
            RAISE one_to_many_issue.
          ENDIF.
        ELSE.
          SELECT SINGLE werks FROM zdef_delplant
            INTO ws_objek
            WHERE cpsloc = ip_cpsplant.
          SELECT auspobjek cabnatnam ausp~atwrt
           INTO CORRESPONDING FIELDS OF TABLE int_plantchar
           FROM ksml AS ksml
           INNER JOIN cabn AS cabn
             ON cabnatinn = ksmlimerk
           INNER JOIN ausp AS ausp
             ON ausp~objek = ws_objek
             AND auspatinn = cabnatinn
             AND ausp~mafid = 'O'
             AND ausp~klart = 'Z01'.
          if sy-subrc ne 0.
            raise plant_not_found_zdef_delplant.
          endif.
        ENDIF.
    *cps plant code is the input parameter. Move objek from table AUSP to
    *ws_objek using inner join of CABN and AUSP to match up the internal
    *characteristic numbers from the 2 tables.
      ELSEIF NOT ip_sisloc IS INITIAL.
        SELECT ausp~objek
          INTO TABLE int_plant
          FROM ausp AS ausp
          INNER JOIN cabn AS cabn
            ON cabn~atnam = 'SISLOC'
              WHERE auspatinn = cabnatinn
                AND ausp~mafid = 'O'
                AND ausp~klart = 'Z01'
                AND ausp~atwrt = ip_sisloc.
    *Checking the existence of ip_sapplant in the table
        IF sy-subrc EQ 0.
          DESCRIBE TABLE int_plant LINES ws_countplant.
    *Moving the values of objek, atnam, and atwrt to PLANTCHAR using objek
    *from ws_objek.
          IF ws_countplant EQ 1.
            LOOP AT int_plant.
              SELECT auspobjek cabnatnam ausp~atwrt
                INTO CORRESPONDING FIELDS OF TABLE int_plantchar
                FROM ksml AS ksml
                INNER JOIN cabn AS cabn
                  ON cabnatinn = ksmlimerk
                INNER JOIN ausp AS ausp
                  ON ausp~objek = int_plant-plant
                  AND auspatinn = cabnatinn
                  AND ausp~mafid = 'O'
                  AND ausp~klart = 'Z01'.
            ENDLOOP.
    *If there more than one SAP Plants, then raise an exception.
          ELSEIF ws_countplant GT 1.
            RAISE one_to_many_issue.
          ENDIF.
        ELSE.
          SELECT SINGLE werks FROM zdef_delplant
            INTO ws_objek
            WHERE sisloc = ip_sisloc.
          SELECT auspobjek cabnatnam ausp~atwrt
           INTO CORRESPONDING FIELDS OF TABLE int_plantchar
           FROM ksml AS ksml
           INNER JOIN cabn AS cabn
             ON cabnatinn = ksmlimerk
           INNER JOIN ausp AS ausp
             ON ausp~objek = ws_objek
             AND auspatinn = cabnatinn
             AND ausp~mafid = 'O'
             AND ausp~klart = 'Z01'.
          if sy-subrc ne 0.
            raise plant_not_found_zdef_delplant.
          endif.
        ENDIF.
      ELSE.
    *Checking if there is an input parameter entered.
        RAISE no_input_found.
      ENDIF.
    Modified 7/30 by RFOR to validate SAP plant is in plant master
      data: wa_t001w like t001w.
      read table int_plantchar.
      SELECT SINGLE * from t001w into wa_t001w where
      werks = int_plantchar-objek.
      if sy-subrc ne 0.
        raise NO_OBJEK_FOUND.
      endif.
    *Moving all the characteristic values to the export parameters
      LOOP AT int_plantchar.
        MOVE int_plantchar-objek TO ep_sapplant.
        CASE int_plantchar-atnam.
          WHEN 'OLDCODE'.
            MOVE int_plantchar-atwrt TO ep_cpsplant.
          WHEN 'SISLOC'.
            MOVE int_plantchar-atwrt TO ep_sisloc.
          WHEN 'OWNERSHIP'.
            MOVE int_plantchar-atwrt TO ep_ownership.
          WHEN 'SMISTYPE'.
            MOVE int_plantchar-atwrt TO ep_smistype.
          WHEN 'SPOTREF'.
            MOVE int_plantchar-atwrt TO ep_spotref.
          WHEN 'SUBTYPE'.
            MOVE int_plantchar-atwrt TO ep_subtype.
          WHEN 'SUPPLYREGION'.
            MOVE int_plantchar-atwrt TO ep_supplyregion.
          WHEN 'TYPE'.
            MOVE int_plantchar-atwrt TO ep_type.
          WHEN 'DISTAREA'.
            MOVE int_plantchar-atwrt TO ep_distarea.
          WHEN 'GEOGAREA'.
            MOVE int_plantchar-atwrt TO ep_geogarea.
          WHEN 'HMF'.
            MOVE int_plantchar-atwrt TO ep_hmf.
          WHEN 'IATACODE'.
            MOVE int_plantchar-atwrt TO ep_iatacode.
          WHEN 'IRSTCN'.
            MOVE int_plantchar-atwrt TO ep_irstcn.
          WHEN 'OPSAREA'.
            MOVE int_plantchar-atwrt TO ep_opsarea.
          WHEN 'PLANTSTAT'.
            MOVE int_plantchar-atwrt TO ep_plantstat.
          WHEN 'PORTCODE'.
            MOVE int_plantchar-atwrt TO ep_portcode.
          WHEN 'REFAREA'.
            MOVE int_plantchar-atwrt TO ep_refarea.
          WHEN 'SAPTYPE'.
            MOVE int_plantchar-atwrt TO ep_saptype.
          WHEN 'MFG_WARRANTY'.
            MOVE int_plantchar-atwrt TO ep_mfgwarranty.
          WHEN 'USER_TYPE'.
            MOVE int_plantchar-atwrt TO ep_usertype.
          WHEN 'TERMINALCENTER'.
            MOVE int_plantchar-atwrt TO ep_trmcenter.
          WHEN 'TRANSPORTATIONCENTER'.
            MOVE int_plantchar-atwrt TO ep_transcenter.
          when 'FEIN'.
            move int_plantchar-atwrt to ep_fein.
        ENDCASE.
      ENDLOOP.
    ENDFUNCTION.
    Pls help me out from this problem its very urgent.
    Thanks

    hi SK ,
    process like this .
    in BADI
    method.
    1.Here u have to put ur logic based on the Requirement.
    2.then u have to call BTE like this
    <b>call function 'OPEN_FI_PERFORM_00001020_E'
          tables
            t_bseg = xbseg
            t_bkpf = xbkpf.</b>
    3.Update Ztables.
    endmethod.
    this is sample logic only.First get logic of TS then u will come to know how to do?
    regards
    prabhu

  • Short Dumps in standard HR Business Event Group/Event creation transactions

    Dear All,
    I m getting short dumps whlile executing standard HR transactions for Creation of Business Event Groups and Business Event Types. Attaching the Short Dump text herewith. Can anyone plz. help...
      An exception occurred that is explained in detail below.
      The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
       not caught in
      procedure "RH_BASE_READ_INFTY_NNNN" "(FUNCTION)", nor was it propagated by a
       RAISING clause.
      Since the caller of the procedure could not have anticipated that the
      exception would occur, the current program is terminated.
      The reason for the exception is:
      Eine Open SQL-Klausel wurde dynamisch angegeben. Der darin auftretende
      Feldname "SUBTY" kommt in keiner der Datenbanktabellen aus der
      FROM-Klausel vor.
    Thanks and Regards,
    Sudipto.

    Hi,
    Check whether the OSS note 207515 is suitable for the below situation.
    Summary
    Symptom
    A dump occurs in program SAPLRHDB: DBIF_NTAB_TABLE_NOT_FOUND
    Additional key words
    RH_BASE_READ_INFTY_NNNN, LRHDBU16
    Cause and prerequisites
    The system wants to access table HRPnnnn  particularly by means of an entry in the infotype check table T777D. This access can be processed in various places, including in the profile generator. Here, a termination occurs if the 'ent' table/structure in the dictionary is no longer available. This generally affcts customer-specific infotypes. These have been created and possibly deleted again. However, the entry in table T777D is not available. You can also import the entry into another system with a transport of the table. If the HRP table/structure is then missing, a termination may also occur in this case.
    Solution
    You must check on an individual basis which infotype the termination refers to. If it is a customer-specific infotype, the customer is responsible for removing the cause of the termination. If the table entry is a 'remnant', the entry can simply be deleted.
    If the termination refers to an SAP structure, you should consult SAP before carrying out any further activities.
    Source code corrections
    Header Data
    Release Status: Released for Customer
    Released on: 23.03.2000  23:00:00
    Priority: Recommendations/additional info
    Category: Customizing
    Primary Component: PA-BC Basis
    Releases
    Release Independant
    Satya

  • Transport of Business System in IDoc scenarios.

    HI All,
    I am doing IDoc scenarios so I am using Business System say PIS_800 . Now i have moved these scenarios to quality system and my Business System name is supposed to be PIQ_800.
    I am using simply file import-export for transport. After transport my Business System name is coming as PIS_800 only.
    Can anybosy plz suggest me how to change it to PIQ_800? This part is quite new to me so detailed explaination will be helpful.
    Thanks,
    Atul.

    Hi Atul,
    In DEV
    1) Export the TS & BS of SAP R/3
    2) Export the TS & BS of DEV XI Server
    In QTY
    1)Import the TS & BS of SAP R/3
    2) Import the TS & BS of DEV XI Server
    3) Create the TS for Quality SAP R/3 & Corresponding BS also which is pointing the QTY Server Details
    Now create the Transport Groups and Targets
    http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
    With this Configuration, the DEV BS will be replaced by the QTY BS.
    Thats all
    Regards
    Seshagiri

  • Business sytem

    Hi,
    can i assign one business sytem to two scenarios in XI-ID, secondly can i assign one technical system to 2 business sytem in SLD.
    regards,
    Gayatri.

    thanks a lot krishna, i will change the message interface and interface mapping every thing in new scenario, may be it will work, let me tell you my project. instead of this primitive questions let me explain u every thing about project.
    1, i need to add the two fields in existing logic, scenario is RFC to .Net., so i added 2 new fields, and mapped with rfc. done, then started trouble, i need to transport this to Prd, suddenly i realized that Prd name space is different than Dev name space in IR.the configuration scenario name also diff in ID. so what to do.
    2, then first thing is to upload the xsdl and change the name space and download to Prd name space, they said no no, you have to develop whole new scenario not touching the old scenario. if it works we will get rid of old scenario slowly, the rfc pointers and business system will be same, so  i developed  a total new scenario(name space) i mean copy old scenario in to new with same message interfaces under same SWCV. when i want to change ID objects it's not allowing me to change, any way I'm not going to trasport id in to Prd, i will manually give the business system and every thing. but i want to make sure that in prod also i can copy the objects, so i think ur advice will work, while coping the scenario in IR i will change all the names. may be then in ID it will alow me to point to same Business sytem. i will try it. this is all about the  My XI project. I'm basically an ABAP, not learned any XI, that is the main reason for this kind of primitive questions.

Maybe you are looking for