EWM: Packaging Specification

Hello,
Do we have any standard transaction for mass creation of packaging specification in EWM?
Thanks
Sharad

Hi,
"Will system create two HUs (100 EA and 30 EA) during the packing function ( Manual Packing) or it will create two WT at the time of final putaway ?"
Depends
There are some places where you can assign the determination procedure to, two are:
- the warehouse number - here you have something for "internal processes" (which is used for putaway and pick strategies), "deconsolidation", and "palletization"
- the inbound document type (specifically the PDI).
If the determination is assigned to the warehouse number as palletization, then the system would create two WTs, one for 100 and one for 30 pcs.
If you have assigned the determination procedure to the inbound delivery, then the system can find the pack spec when you go to the manual packing from the inbound delivery. But I think you also have to flag "no automatic packing" in the inbound delivery doc type then. And you need to mark in the pack spec the flag "create HU" on the packing level. If the flag "no automatic packing" is not set, but the "create HU" flag is set, then HUs are automatically created in the inbound delivery.
"Also I am not clear why there are different condition type for different processes ? I can use the same condition for palletization and inbound process but not sure why different conditions are provided here , I would appreciate if you can help me to understand this.."
Well, there might be cases that in fact you can use the same pack spec for different processes. But for example often a pack spec for a pick HU (where you might pick several materials and the system shall find the best packing material) will not look like a palletization pack spec (where one specific material is packed according your agreement with the vendor).
Different conditions are provided, that does not mean you have to use them.
Brgds
Juergen

Similar Messages

How to open and compile a package specification and body in SQL Developer

I'm currently evaluating a possible migration to SQL Developer.
Our PL/SQL code base is stored in scripts files named as follows: <schema>.<package_name>_<package|package_body>.sql and managed in SVN.
If now trying open a sql script containing the package specification or body and trying to compile it, I get no or strange error messages as if SQLDeveloper would not recognize the source as a PL/SQL code.
If I open an already compiled package from the database it seems to work as expected.
On the other hand I cannot find any option to write a package specification or body to a script except for the "Save package spec and body" option that only generates a single (!) script containing package specification and body in one single file and without any configuration options on how to name the generated file.
Any help is appreciated!

What strange error messages ? Make sure to configure your extensions as PL/SQL file type under Preferences - File Types.
To save, just Save As under the File menu.
Hope that helps,
K.

Error message when activation a packaging specification in ICH 5.0

Dear all,
I created a packaging spec within ICH 5.0. The check function does not return a error. But when trying to activate the PS I am getting the error message:
Package specification not activated; no condition records found.
What kind of condition records does the system mean?
Regards
Martin

Hi Martin,
You can have a look in the pack spec group and make sure that the flag 'PS_ACTIVATE' it is not set.
That way you will no longer face this error during the activation process.
I hope this will help you.

Global Variable in Package Specification

Hello,
I created global variable in package specification,
Is it valid for the current session or it will work for all the session.
Thanks,Kannan.K

Package varaibles are session bound, to demonstrate, a simple test:
--session 1:
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
SQL> exec dt_test_pack.set_global(50);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
        50
--Session 2 at the same time
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
SQL> exec dt_test_pack.set_global(100);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
       100
--Back to session 1:
SQL> exec dt_test_pack.set_global(null);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
--Back to session 2:
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
       100HTH
David

Grant Execute on package Specification

How to give grant to package specification to another user?
The package has only specification and no package body
in package specification i have defined some constants variables which i need to access from another user?
Current if i give grant execute from the other user it is shwoing up only blank body......

Works for me...
As test_user...
SQL> create or replace package test_vars is
2 g_number number := 100;
3 end;
4 /
Package created.
SQL> grant execute on test_vars to scott;
Grant succeeded.As scott...
SQL> create synonym test_vars for test_user.test_vars;
Synonym created.
SQL> set serverout on
SQL> begin
2 dbms_output.put_line(test_vars.g_number);
3 end;
4 /
100
PL/SQL procedure successfully completed.
SQL>

[4.0 EA2] - Shift + F4 does not open the package specifications

Hi,
I tried opening the package specifications by clicking on the package name in a worksheet and then doing a Shift+F4 but it did not work.
This used to work on 4.0.0.12.27. Is this a bug?
Regards,
Sujoy

There are some errors thrown into log when this happens.
Level
Source
Message
SEVERE
oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$1
node has no children at javax.swing.tree.DefaultMutableTreeNode.getChildAt(DefaultMutableTreeNode.java:243)
WARNING
org.openide.windows.WindowManager
[Winsys] TopComponent com.oracle.jdeveloper.nbwindowsystem.NbEditorContainer throws runtime exception from its componentActivated() method.
Please repair it!

Security package specific error occurred when trying to connect to Orchestrator with remote Runbook Designer

When I try to connect to Orchestrator server with Runbook Designer installed on my laptop I get an error saying "A security package specific error occurred.".
Entry from Designer log file is below. I've tried to set error level to 3 and 7 but got no additional info about the error. I'm unable to find any details of the error on server or client side in any logs (Event Log or Orchestrator trace logs).
Connecting to Orchestrator Management Server with local Designer installed on the server works fine.
Orchestrator is installed in AD environment and security groups are properly configured.
Can anybody help?
2012-06-12 11:35:51 [7472] 1 Exception caught in long __cdecl `anonymous-namespace'::connectCommunicator(struct HWND__ *,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &)
Connections.cpp(238):
<Exception>
<Type>Opalis::Exception</Type>
<Location>
void __thiscall ServiceCommunicator::connect(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &)
ServiceCommunicator.cpp(118)
</Location>
<MsgCode>A security package specific error occurred.
</MsgCode>
</Exception>

I'm having a similar issue with one of our runbook servers. i cannot deploy any IPs to it. I get the error "A security package specific error occurred". I can open the designer on the runbook server, connect to the management server, and look at
runbooks. They wont run on the server without the IPs though, but it doesnt seem like a connection issue. i have also tried uninstalling/re-installing the runbook server and i get the same.
Has anybody else run into this?
Edit:
Heres an error fromthe event log:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server <Service Account>. The target name used was HOST/server.domain.domain.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can
occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also
happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to
use the current password. If the server name is not fully qualified, and the target domain (domain.domain.COM) is different from the client domain (domain.domain.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified
name to identify the server.
So maybe I was just given the wrong account.
- Slow is smooth and smooth is fast.

Why Package Specification only in INVALID State

Hi All,
Why Package spec is going to invalid state when I change a Procedure which is called in Package body
and why package body is still in VALID state. Can some one please clarify my doubt.

May be only specification got errors and not the package.
May be the constants / variables declared in package specification has wrong reference
like var1 tab1.col1%type which column doesnexists....
OR
V number(1) :=10;
or
improper closing / ending of a procedure..

Blanck Package Specifications

Hi,
Today, a lot of our customers (50%) has called us with multiples PL/SQL errors.
In fact we seen that a lot of Package specifications remain blanck !
We use both 9i and 11g versions.
Any idea ?
Thanks

872006 wrote:
I'm sorry but this is the first time that i post on this forum.
My goal is not to prove that Oracle has a problem but to understand what happened...
In packages specifications there were only basic code such like 'create or mofify...' and '/* place your code here */
It is just like the package specification was just created (The package body were Ok)
Is there any worm able to do this bad job and how can i find it ?
ThanksI don't know what you have.
I don't know what you do.
I don't know what you see.
It is really, Really, REALLY difficult to fix a problem that can not be seen.
use COPY & PASTE so we can see what you do & how Oracle responds.

Package specification and must be defined in the package body

Hi All
While creating bellow Package, following error occured. Plese guide me.
SQL> ;
1 create or replace PACKAGE Fresh_Movement IS
2 Procedure Opening_cx (P_Yeay Number,p_Week NUmber);
3* END Fresh_Movement;
SQL> /
Package created.
CREATE OR REPLACE PACKAGE BODY Fresh_Movement IS
Procedure Opening_Cx (pYear Number, pWeek in number) Is
     Cursor Cx_nCou Is Select C.LOCATION_KEY,NVL(C.CUSTOMER_CATEGORY_FRESH,'X') Category,Count(C.CUSTOMER_CATEGORY_FRESH)nCou
     From Customers C
     Where Trunc(C.Start_date) <= ( Select Trunc(max(END_DATE)) From CUSTOMER_CALENDAR
where ALMARAI_YEAR = pYear and ALMARAI_WEEK= pWeek - 1 )
AND Active = 'Y'
Group by C.LOCATION_KEY,C.CUSTOMER_CATEGORY_FRESH
Order by 1,2;
Begin
For Tmp_rec1 In Cx_nCou Loop
     Insert Into Trading_fresh_Movement (YEAR,WEEK,LOCATION_KEY,CX_CATEGORY,COUNT,COLUMN_TYPE,SEQ )
     Values (pYear,pWeek,Tmp_rec1.LOCATION_KEY,Tmp_rec1.Category,Tmp_Rec1.nCou,'OPN',1);
End Loop;
Commit;
End Opening_Cx;
END;
Warning: Package Body created with compilation errors.
SQL> show error
Errors for PACKAGE BODY FRESH_MOVEMENT:
LINE/COL ERROR
2/12 PLS-00323: subprogram or cursor 'OPENING_CX' is declared in a
package specification and must be defined in the package body
SQL>

The signature of the procedure in the specification and in the body must be the same. This includes the name of the parameters.
Change the specification to
create or replace PACKAGE Fresh_Movement IS
   Procedure Opening_Cx (pYear Number, pWeek in number);
END Fresh_Movement;
/

Package specification

5) package specification
x number :=10;
session A
begin
x :=20;
end ;
session B
y:=x;
what is the value of Y now . both session are connected at same time ?

Even though the session are started at same time package variable are stored separetly for each session. they will be processed separatly in PGA for each session . So in session B the value of y is 10

Cannot deploy process flow package specification from file

Hi,
we are using owb 11gr2 on linux. We successfully managed to deploy mappings and tables into a specification file, and then deploy from that file into the target database (RAC). But when we try to deploy a process flow package we run into an error:
A process flow package can be deployed to a specification file. But a deployment from that specification file fails with the error: " OMB05623: Cannot deploy specification from file. Exception follows. nulll"
### SETUP
set CONN_DESIGN "xxx"
set CONN_TARGET_DESIGN "yyy"
set CONN_TARGET_RT "xxx'"
set DIR "D:\\tmp"
set RELEASE "V0_2"
set file "$DIR\\$RELEASE"
set plan "FILE_DEPLOY_$RELEASE"
### Deployment via control center: works!
OMBCONNECT $CONN_DESIGN
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBCC '/KLINGEL_DWH'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan'
OMBDISCONNECT CONTROL_CENTER
OMBCOMMIT
OMBDISCONNECT
### Deployment via specificatin file: fails!
OMBCONNECT $CONN_DESIGN
OMBCONNECT CONTROL_CENTER $CONN_DESIGN
OMBCC '/KLINGEL_DWH'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan' AS SPECIFICATION TO '$file.xml'
OMBDROP DEPLOYMENT_ACTION_PLAN '$plan'
OMBDISCONNECT CONTROL_CENTER
OMBCOMMIT
OMBDISCONNECT
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBDEPLOY SPECIFICATION FROM '$file.xml'
### OMB05623: Deployment von Spezifikation aus Datei nicht möglich. Exception folgt. null
###OMB05623: Cannot deploy specification from file. Exception follows. nullIf we use the operation DROP it works. But REPLACE and CREATE do not work.
We get the error regardless whether the code is executed as an expert or on the command line at a windows client.
Does anyone knows a workaround?
Deployment via a specification file is a must due to license and architecture requirements.
Thanks,
Carsten.

Its woked fine for me for OWB 10.2.0.4 .... some steps are missing from code like
when you are connecting again it should be
OMBDISCONNECT
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
OMBDISCONNECT
OMBCC '/KLINGEL_DWH'
OMBCONNECT CONTROL_CENTER $CONN_TARGET_RTI think you can try the same on different system .
Cheers
Nawneet

Global Variables across sessions in PL/SQL package Specification

Hi,
Is there a way I can share a variable value across sessions that doesnot affect by Commit/rollback.
The value would be set by one session and is visible across sessions, until it is set to another value by another/same session, and the new value is visible across.

V$Session is not granted to the user executing this. So, had to go with the context. Finally could resolve with the following code.
Run by DBA
create or replace context ctx1 using USER_procowner.pkg_global accessed globally;
grant execute on dbms_session to USER_procowner;
Run by user_procowner
create or replace package user_procowner.pkg_global AS
procedure set_lock(in_val IN VARCHAR2);
Function get_lock RETURN VARCHAR2;
end pkg_global;
create or replace package body user_procowner.pkg_global AS
procedure set_lock(in_val IN VARCHAR2) IS
begin
dbms_session.set_context('ctx1','var1',in_val);
end;
Function get_lock RETURN VARCHAR2 IS
begin
return (Sys_context('ctx1','var1'));
end;
end pkg_global;
grant execute on pkg_global to user_procuser;
exec user_procowner.pkg_global.set_lock('Y')
select user_procowner.pkg_global.get_lock Lock from dual;
LOCK
Y
exec user_procowner.pkg_global.set_lock('N')
select user_procowner.pkg_global.get_lock Lock from dual;
LOCK
N
The current value of var1 is visible across sessions using user_procowner.pkg_global.get_lock.
Thanks to all contributors.

SQL Agent job step - SSIS package - adding a config file - will it override the one that the package specifies?

If I setup a job step to run a package and set the config file location on the "Configurations" tab, will that override the config file that the SSIS package is configured to use? Or is this a "cumulative" type configuration option?
I typically have my config file mixed in with my project files, but that path wont exist on the server.

Hi Shiftbit,
ETL vs ELT is right.
In SSIS 2005, the DTExec utility loads and runs the package, events occur in the following order:
The package file is loaded.
The configurations specified in the package at design time are applied in the order specified in the package (except for Parent Package Variables).
Any options specified from the command line are applied. Any configurations specified on the command line overwrite the current values; however, they do not trigger a reload of the configurations if a changed value impacts a configuration dependency. For
example, if the connection string used for SQL Server configurations is updated from the command line at run time, the package will still retain any other values from the design-time SQL Server configuration database.
Parent Package Variable Configurations are applied.
The package is run.
In SSIS 2008 and higher, utility loads and runs the package, events occur in the following order:
The dtexec utility loads the package.
The utility applies the configurations that were specified in the package at design time and in the order that is specified in the package. (The one exception to this is the Parent Package Variables configurations. The utility applies these configurations
only once and later in the process.)
The utility then applies any options that you specified on the command line.
The utility then reloads the configurations that were specified in the package at design time and in the order specified in the package. (Again, the exception to this rule is the Parent Package Variables configurations). The utility uses any command-line
options that were specified to reload the configurations. Therefore, different values might be reloaded from a different location.
The utility applies the Parent Package Variable configurations.
The utility runs the package.
So, we can see that no matter we use SSIS 2005 which applies the Configurations once or use SSIS 2008 (or higher) which applies the configurations twice, the configurations specified in the command line will affect and not be overwritten by the configurations
specified at design-time.
Reference:
http://technet.microsoft.com/en-us/library/ms141682(v=sql.110).aspx.
Regards,
Mike Yin
TechNet Community Support

Effects? changing of package specification in .pll

dear all,
Have you experience the following problem:
I have a library attached to several forms. these form share some context data in this library (i always use call_form with share_library_data option). I add a procedure to one package in the library mentioned and attach it to a new form. This form and the old forms couldn't share the context data in the library.
I solve it problem by delete the attachment in all the old form, reattach the library and compile all the forms. Since I have a great number of the old forms, it is not pratical thing to do.
Is it the only way to do it ? or is there any elegant solution ?
what happens here?
Please help
null,

Look at it from the database's perspective: Forms has a where clause that it sends to the database that contains a reference to a package variable that reside on the client. What can the database do with that? It knows nothing about client side package variables. How would it discover and substitute that reference with the value of the client's package variable?
Now look at it from Forms' perspective: you have declared a where clause that you know contains a reference to a package variable. How will Forms know to substitute the reference for the actual value? With Forms items you use the semicolon notation but for package variables there is no analog.
You need make the full where clause yourself including substituting the reference for the the actual value. The way to do that is with set_block_property and the DEFAULT_WHERE.
From the help file:
"DEFAULT_WHERE sets the WHERE clause on the block and OVERRIDES the value set at design time.
The WHERE reserved word is optional. The default WHERE clause can include references to global variables, form parameters, system parameters, and item values, specified with standard bind variable syntax."

EWM: Packaging Specification

Similar Messages

Maybe you are looking for