Different Chnage management Tables in ECC and relation

Dear BW/ECC experts..
I wish to find out if you have any document or link to read on the change management tables in ECC in relation to BW.
Like JEST/JCDS tables gives Changes to USER/SYSTEM status change....
JEST
JCDS
CDHDR
CDPOS
AENR
AEOI
I know this may not be directly relavant for BI/BW but some of you might have already gone thru this process.
Thank you in advance.

Hi,,,,,,, you Can refer the below links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0002c1c-f07c-2c10-3c93-b053715529b4?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00f47333-a50e-2e10-a7bf-d0ab463da382?quicklink=index&overridelayout=true

Similar Messages

  • Case Management - Table to find out relation between Case and Activity

    Hi.
    I do search the SDN for the same quesiton, I found one but it was not answered by a single person. So let me ask it again:
    I am working on an interface in CRM that will create the activity and link it to the open case.
    I can get the existing case GUID and information from table CRMD_CMG_CASE_AT .
    I can get the GUID as a return parameter when activity will be created using BAPI.
    But how can I link the activity to the case.
    1. Which table is having relation between both case and activity?
    2. What class or BAPI will be used to link created activity to existing case?
    Thanks in advance.
    Hitesh

    done

  • Which table stores site and related category info

    Hello all,
    Can anyone tell me in which table or view I can find to which category a content area belongs. I browsed through the tables and the WWSBR_SITE_CATEGORY$ table looked promising, but this is not the right table.
    Thanks for any clue.
    Onno

    Onno,
    A content area does not belong any category. In other words, you cannot assign a category to a content area.
    To look at all the categories that belong to a content area, look at the public view wwsbr_all_categories.

  • Case Management - table linking activities and cases

    Hi.
    I need to create a report in CRM that shows cases and the service orders that are linked to them.
    I can get the case information from table CRMD_CMG_CASE_AT for example.
    I can get the service order information from table CRMD_ORDERADM_H.
    But how can I link the two tables?  Is there a table that contains both the Case GUID and the Order GUID?
    Thanks in advance.
    Ian.

    The way I have worked by linking these data is:
    CRMD_CMG_CASE_AT-CASE_GUID = SCMG_T_CASE_ATTR-CASE_GUID
    then
    SCMG_T_CASE_ATTR-EXT_KEY = CRMD_ACTIVITY_H-EXTERN_ACT_ID (be careful because EXTERN_ACT_ID is char(20), so you need complete with 0 left zeros the empty positions, for ie: ext_key 2032 is equal to 000000002032 EXTERN_ACT_ID)
    then
    CRMD_ACTIVITY_H-GUID = CRMD_ORDERADM_H-GUID
    I hope it'll be useful. Regards
    Nati

  • Replication Z-Tables from ECC to CRM

    We have a client with some Z-Tables in ECC and we need to replicate this tables in CRM,  anybody have any information about this.
    Thanks in advanced
    Sebas

    Hi Sebas,
    The following link shows the replication from CRM to ECC. The same can be followed for replication from ECC to CRM.
    Replication of Z table from CRM to R/3 - No mBDoc Created
    You can also try this
    1. Create the Ztables both in ECC and CRM
    2. create customizing adapter objects in R3AC3.
    3. copy the stanadard FM 'CRM_BUPA_MAP_ADREREG_CI' to custom FM and write source code. load object in R3AS.
    4. create a variant and shedule the based on requirement
    Thanks and regards,
    Madhukar Reddy

  • Different types of tables and purpose

    Hi,
    Could someone explain me the different types of tables an what data they store.
    Sonali

    hi Sonali,
    These are the different types of tables in MDM
    Flat Tables : It is a simple table consisting of record and fields ( rows and column) .
    Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
    Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
    Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
    Tables are also Categorized as Object Tables like :
    Images : This table is for storing Images
    Sounds : This table is for storing Sound File.
    Videos : This table is for  storing Video Files .
    Binary Objects : This table is for storing Binary Objects.
    Text Blocks : This table is for storing  block of text.
    Copy Blocks : This table is for storing  block of text interpreted as a Copy.
    Text HTML`s : This table is for storing  block of text interpreted as a HTML.
    PDFs : This table is for storing PDF files.
    There are various types of Special Tables , i have mentioned below:
    Image Variants : Used to define the structure
    and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
    Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
    Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
    Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
    Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
    Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
    Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
    There are various types of System Tables :
    Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
    Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
    Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
    Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
    Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
    Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
    Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
    XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
    Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
    Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
    In MDM SP06 5.5 we can have only one main table, but in MDM 7.1 version we can maintain many main tables.
    Rewards points if helpful
    Regards,
    Vijay

  • Different types of tables and modes

    Hi Experts
    What is the specification of different tables in console and different modes in data manager.
    What is the major difference between them.
    Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
    have fun..
    Hari

    Hi Hari,
    Differnt types of tables in Console are :
    Actually the Tables in Console are further categorized as :
    Main Table and Sub table which include:
    Flat Tables : It is a simple table consisting of record and fields ( rows and column) . In MDM Main table is always a flat table.
    Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
    Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
    Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
    Tables are also Categorized as Object Tables like :
    Images : For storing Images
    Sounds : For Sound File.
    Videos : For storing Video Files .
    Binary Objects : To store Binary Objects.
    Text Blocks : To store block of text.
    Copy Blocks : Stores block of text interpreted as a Copy.
    Text HTML`s : Stores block of text interpreted as a HTML.
    PDFs : To store PDF files.
    There are various types of Special Tables also:
    Image Variants : Used to define the structure
    and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
    Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
    Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
    Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
    Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
    Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
    Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
    There are various types of System Tables :
    Roles :  A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
    Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
    Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
    Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
    Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
    Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
    Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
    XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
    Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
    Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
    Data Manager:
    Data Manager in simple terms can be stated as a place where we manage the data that is taken from various systems.
    All the data that you take from all the various systems that a business is using is then taken into data manager, so that it could be cleansed and can be maintained easily in future.
    There are basically four different modes in Data Manager:
    1. Record Mode:  This mode allows us to search, view and edit the records of any table in MDM repository. This is the mode that one uses most often, primarily to view and edit records in the main table and also to view and edit records in any of the sub tables.
    2. Hierarchy mode. This mode allow us to view and edit the hierarchy tables in the MDM repository, including regular hierarchy tables, taxonomy tables, and the Masks table. Though we can also view and edit the records of a hierarchy table in Record mode, Hierarchy mode specifically allows us to edit the parent/child relationships and the sibling ordering of the hierarchy.
    3. Taxonomy mode. This mode allows us to view and edit the taxonomy tables in the MDM repository. We usually use this mode to create and maintain the category hierarchy used in the repository, and to manage the attributes associated with each category and subcategory. Though we can also view and edit taxonomy tables in both Record mode (for searching) and Hierarchy mode (for editing the other fields of information associated with each category), Taxonomy mode is unique in that instead of focusing on the records of the taxonomy table, it allows you to create and manage the pool of attributes associated with the taxonomy table, and to assign attributes to categories on a category-by-category basis.
    4. Matching mode.  This mode allows us to identify and eliminate duplicate records within an MDM repository. When you view the main table in Matching mode, MDM allows you to perform u201Cmatching-and-mergingu201D on and against any or all of its records, using various user-defined criteria (like creation of Rules and Strategies) to decide whether or not records are potential duplicates.
    5. Family mode. This mode allows us to view and edit the Families table, which layers a hierarchy of families upon the taxonomy hierarchy to further break down each category into smaller groups of main table records. We usually use this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each family of main table records rather than each individual record.
    Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
    The structure of the tables are defined in Console and those tables are then used in Data Manager, but if you have defined a table as a Hierarchy table you cannot use that table in Taxonomy Mode but you will be able to see all the tables in Record Mode.
    Hope this would be useful...
    If useful do reward points!!!!
    Regards,
    Parul

  • Database table/FM to find relation between plant and company code in SRM

    Hi,
    I have a requirement where I need to determine the relation between the plant and company code in SRM.
    The plant and company code both belong to R/3. We are replicating the plant by using the report BBP_LOCATIONS_GET_ALL.
    This plant is now available as a BP in SRM. But from which SRM table or using which SRM FM can I get the relation between this and the company code?
    Thanks,
    Srivatsan

    Hi
    <b>Check table BBP_LOCMAP. (Plants) -  Manage Table Business Partner   > System   > Location
    BBP_COMPCODE_FAV               User-Specific Favorites for Permitted Company code.</b>
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • Syntax of DDL options and related (table) column names

    Hi,
    where can I find something like a mapping between DDL options and related table column names?
    For example I do have the table options PCTFREE, FREELISTS and NOCOMPRESS. The related table columns out of user_tables are PCT_FREE, FREELIST and COMPRESS.
    PCT(_)FREE wins an Underscore, FREELIST(S) wins an "S" and it is "NOCOMPRESS" if COMPRESS has a value "Y(es)".
    Hope somebody can help.

    So far I didn't find any information that is not in
    the DDL script gernerated from
    DBMS_METADATA.get_DDL.Alright, I give you an example:
    I create a table with the following DDL:
    "CREATE TABLE IntBuch (
    int_bunr integer NOT NULL,
    int_sdat double precision NOT NULL,
    int_hblz char(8) NOT NULL,
    int_hkto char(7) NOT NULL,
    int_hdat double precision NOT NULL,
    KtoNr char(7) NOT NULL,
    BLZ char(8) NOT NULL,
    CONSTRAINT PK_IntBuch PRIMARY KEY (int_bunr)
    USING INDEX
    PCTFREE 10
    STORAGE (
    INITIAL 1000
    NEXT 500
    PCTINCREASE 0
    MINEXTENTS 1
    MAXEXTENTS 4096
    PCTFREE 20
    LOGGING
    CREATE UNIQUE INDEX intid
    ON IntBuch (int_bunr DESC)
    CREATE INDEX hkto
    ON IntBuch (int_hblz,int_hkto)
    COMMENT ON TABLE IntBuch
    IS 'Kommentar zu DB-Tabelle InBuch'
    COMMENT ON COLUMN IntBuch.int_sdat IS 'Kommentar zu DB-Spalte int_sdat'
    ALTER TABLE IntBuch
    ADD CONSTRAINT Gutschrift FOREIGN KEY (int_hkto,int_hblz) REFERENCES Konto
    ON DELETE CASCADE
    ADD FOREIGN KEY (KtoNr,BLZ) REFERENCES Konto
    ADD FOREIGN KEY (int_bunr) REFERENCES Buchung
    ON DELETE CASCADE
    After that I read the DDL with DBMS_METADATA.get_DDL and I get
    " CREATE TABLE "UOENDE"."INTBUCH"
    (     "INT_BUNR" NUMBER(*,0) NOT NULL ENABLE,
         "INT_SDAT" FLOAT(126) NOT NULL ENABLE,
         "INT_HBLZ" CHAR(8) NOT NULL ENABLE,
         "INT_HKTO" CHAR(7) NOT NULL ENABLE,
         "INT_HDAT" FLOAT(126) NOT NULL ENABLE,
         "KTONR" CHAR(7) NOT NULL ENABLE,
         "BLZ" CHAR(8) NOT NULL ENABLE,
         CONSTRAINT "PK_INTBUCH" PRIMARY KEY ("INT_BUNR")
    USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
    STORAGE(INITIAL 16384 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "USERS" ENABLE,
         CONSTRAINT "GUTSCHRIFT" FOREIGN KEY ("INT_HKTO", "INT_HBLZ")
         REFERENCES "UOENDE"."KONTO" ("KTONR", "BLZ") ON DELETE CASCADE ENABLE,
         FOREIGN KEY ("KTONR", "BLZ")
         REFERENCES "UOENDE"."KONTO" ("KTONR", "BLZ") ENABLE,
         FOREIGN KEY ("INT_BUNR")
         REFERENCES "UOENDE"."BUCHUNG" ("BU_NR") ON DELETE CASCADE ENABLE
    ) PCTFREE 20 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "USERS"
    If there are no more DDLOptions possible than that, it is fine for me. If not, but all kinds of options are to find in only one or two tables of the database ( user_tables for table options, dba_constraints and dba_segments for column options, primary and foreign keys, user_indexes and user_segments for indexes ...), that is fine for me, too. (As long as I get to know which tables are "sufficient" for that.) If it is different than both of that, that's bad.
    However if you want to use defaults instead of
    absolut values, it is better to remove certain parts,
    like the storage clause, from the generated output.I understand this, but I am more interested to have all and not leaving out some of them in order to have the defaults in the database after running the DDL.
    A totally different approach could be to
    a) create a database link from one DB to another.
    b) create table <new_table> as select * from
    <old_table@dbLink> where 1=2;I keep that in mind, thanks for that hint.

  • Table and related table keys

    Hi, 
    Have two tables, related, and wish to not use form / subform to handle relationship.
    What is the best way to assign PK in primary table to FK in related table?
    L
    Leon

    Have two tables, related, and wish to not use form / subform to handle relationship.
    What is the best way to assign PK in primary table to FK in related table?
    Hi Leon,
    I don't know what the underlying thought of your question. And also why you do not wish to use the form / subform relationship. I think you mean the parent-child relation? In all my applications I do not use that parent-child relation either. In fact
    what is normally used as a subform is in my systematics another main form. This gives me the possibility to "walk along relations" in a two-way direction, for any relation.
    I am sure there are more best ways for the PK. For every table I use an autonumber PK. The FK in a related table is of type long. I have experienced that the shorter the key is, the faster the retrieval is. And the long type is in my opinion the
    best.
    Using a strict naming convention for the field of the PK related to its table, and the field of the FK, I have managed that all relations are generated completely automatic.
    Imb.

  • Doc listing all OBIA RPD Projects and related Subject areas and Presentation tables.

    Hi All,
    Can anyone help with the Oracle document ID which gives the RPD Projects and related Subject areas only and Presentation tables.
    I tried using the documentation utlity but it is unable to give me result according to the RPD Projects.
    Thanks,
    Dev

    It is combination of different activities:
    Product guide, check here cool-bi.com
    RPD documentation based on prod guide.
    There might be a project called Project and try to import rpd contents into another then generate rpd doc.
    if helps mark

  • Datasources and Tables in ECC

    Hello, i have to get data from different tables like REGUH, BSIK, BSAK etc. I already checked and there is no datasource that SAP delivers so should i create a customized datasource for each of these and join data in bi? thanks.

    Hi,
    You have to give relation as mentioned below.
    lets take you have X and Y fields are common in all 4 tables. then join condition follows as mentioned below.
    Table A - X = Table B - X
    Table A - Y = Table B - Y
    Table C - X = Table B - X
    Table C - Y = Table B - Y
    Table C - X = Table D - X
    Table C - Y = Table D - Y
    Table A - X = Table D - X
    Table A - Y = Table D - Y
    The relation should be as mentioned above. As we have so many relation we may get performance issue.
    If you face any performance issue try to use Infoset query or function module based generic DS.
    Regards,
    Venkatesh

  • ECCS - Combining statutory and management reporting thru ECCS

    Hi,
    We use ECCS for Company based consolidations. Our statutory reports are from ECCS and Management reports are from PCA. We want to combine these 2 and use ECCS for both kinds of reporting. However, the challenge we have is we don't have the PC in Company based consolidation.
    We want to bring in PC as an attribute to enable management reporting out of ECCS. I am trying different options to pull in PC to ECCS. I have the following questions in this regard.
    1. Has any one ever tried this before?
    2. What are the best practices (Modify exisitng dimension or create a new one etc..)
    3. Is there a brief how-to document that you can share with me.
    Please let me know your thoughts.
    Best Regards,

  • Different Tax codes in SRM PO and replicate ECC PO

    Hello Experts,
    Problem related to the TaX code in replicated PO .
    We are in Extended classic scenario.
    In SRM, when creating Shopping cart we enter manual tax code like e1(20%) or e2(25%) etc and when PO gets generated and replicated in the backend the tax code changes from E1 to V4.
    Now in SRM PO the tax code is E1 and in backend replicated PO the tax code is v4.
    I have checked the condition records in MEK3 t-code in ECC and found that condition record for same region is v4, i think because of this condition record the system is overwriting the tax code which is coming from SRM system.
    Irrespective of any tax code which is coming from SRM PO , the ecc PO overwrites the V4 tac code for same region.
    How i can overwrite that the SRM and ECC should have the same tax code as chosed in SRM at the time of creating a SC or a PO
    Please help to accomplish
    Thanks
    Smriti
    Edited by: Smriti arora on Jan 19, 2011 10:40 AM

    Hello Experts,
    I have posted a thread 3 days back, any help will be greatly appriciated.
    Smriti
    Edited by: Smriti arora on Jan 24, 2011 1:03 PM

  • Configuration related to PO colabration in ECC and SNC

    Hi
    Can anybody throw light configuration related to PO colabration in ECC and SNC.
    Regards
    Raj

    Hi Raj,
    Below link provide you SNC information about Integration ECCPISNC and functionality of SNC
    link http://help.sap.com/saphelp_snc70/helpdata/EN/b4/f20483605b0d4fa856354a986e900d/frameset.htm but if you want configuration document then Click on below link
    http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
    A07_BB_ConfigGuide_EN_DE.doc (Kanban processing)
    S32_BB_ConfigGuide_EN_DE.doc (SCM setting)
    S34_BB_ConfigGuide_EN_DE.doc (Supplier)
    S55_BB_ConfigGuide_EN_DE.doc (Contract Manufacturing Procurement)
    hope this documents are useful.
    Thanks,
    Nikhil

Maybe you are looking for