Skip to Content
avatar image
Former Member

Transport error from SAP HANA Dev to Production

Hi All,

I am new to this.

We are getting errors while transporting Delivery Unit from Dev to Production since the schema name are different in dev and production.

In dev, it is SAPHBD and in production, it is SAPHBP.

I have done mapping in Production Environment and specified Authoring Schema as SAP HBD(DEV) and Physical Schema as SAP HBP (Prod). After doing the mapping, again tried to import via below steps, transport still fails.

Steps taken while transporting:

1. In Development HALM, Export the Delivery Unit. It downloads as .tgz extension on local machine.

2. In Production HALM, Import the above delivery unit. It gives error at this step only and never uploads anything to Production.

Please note that SAPHBD is a secondary schema which we need to refer to get some data from ERP. There are queries like SELECT * FROM SAPHBD.XXTABLENAME in HBDPROCEDURE which are actually failing and giving errors. The actual schema is 'manage_cashier' and it is being created using HBDSCHEMA and database tables using HDBDD files.

Do we need to follow some other steps for creating schemas manually before we do a transport OR it automatically creates the schema and database tables during delivery unit transport?

Error Snapshot as below:

[pshanabw1][HBP][‎7‎/‎27‎/‎2017 ‎4‎:‎55‎:‎19‎ ‎PM][Activation][8] Object: C****Mat.Procedures.PullCashierLeaveData.hdbprocedure ==> Error Code: 40300

[pshanabw1][HBP][‎7‎/‎27‎/‎2017 ‎4‎:‎55‎:‎19‎ ‎PM][Activation][8] Dependent object not found: SqlScript; SAPHBD./BI0/SEMPLOYEE: symbol not found

Regards,

Dolly Kansal

Add comment
10|10000 characters needed characters exceeded

  • Schemas and tables delivered as design time artifacts (e.g. via HDBSCHEMA, HDBDD) are created automatically when the delivery unit or a change list is imported.

    But as I understood you, you have queries in your procedures which uses objects from the SAPHBD schema. As procedures do not support schema mapping the activation of that procedures will fail, cause you do not have such a schema on your production system (as I understood).

  • Former Member Florian Pfeffer

    Thanks for the reply Florian.

    Could you please also elaborate on the possible options I have to solve it?

  • Get RSS Feed

1 Answer

  • Aug 09, 2017 at 08:19 PM

    In a procedure you can define a default schema. You could set the default schema to an authoring schema for which a mapping is defined to the physical schema, because for the default schema the schema mapping is applied.

    You have to consider that you have to remove the schema name from the procedure body for all artifacts (e.g. tables) from which you wanna query the data laying in the default schema.

    For instance:

    PROCEDURE "MISC"."test.misc.procedures::P_TEST_SCHEMA_MAPPING_FOR_PROC" ( )
       LANGUAGE SQLSCRIPT
       SQL SECURITY INVOKER
       DEFAULT SCHEMA AUTHORING_SCHEMA
       READS SQL DATA AS
    BEGIN
       select * from TESTTAB;
    END;
    
    Add comment
    10|10000 characters needed characters exceeded