Compound attribute and transactional attribute

hi experts,
what is compound attribute and transactional attribute, in what case we will use this attributes, can anybody explain with business scenario, pl help to understand this.
thanks & regards
venkat

Coumpounding attributes is an attribute which is compounded with another infoobject. This brings unique data relationship. Suppose u have company codes like CC1, CC2, CC3 and you have employees E1, E2, E3...The employees codes will be same in each company code. To make them unique across we compound the employeee code with company code. The it will result as below.
CC1 - E1, E2, E3
CC2 - E1, E2, E3
CC3 - E1, E2, E3
Again the other one must be a transitive attribute and not transactional attribute. When an navigational acts as another attribute as navigational attribute then the other is called transitive attribute.

Similar Messages

Display entity-attributes and global-attributes in the same screen

Hi,
I have a question about entity.
Is it possible to display in the same screen, entity-attributes and global-attributes?
thanks
Rosalia

Hi Rosalia,
You can only display attributes from the current entity and the entity or entities that it is contained by (the parent entities).
So if you had the following data model
Global
..the person
...the income
the person is contained by global.
the income is contained by the person (which is contained by global).
If you want to create a person-level question screen, you can display global attributes on that screen by using subsitution like %global_field_1%. You cannot, however, input global attributes on that screen (ONLY attributes belonging to the person)
If you want to create an income-level question screen, you can display attributes from the person such as "tell us about %person_name%'s income..." as well as global attributes. Again, you cannot input person or global attributes on that screen (ONLY attributes belonging to the income)
However it only works from child-to-parent containment relationships! You cannot have a global question screen which loops through the person instances and displays attributes from the person, or from the income out-of-the-box.
We have managed to implement this using custom controls.
You can map individual attributes back up to the parent level, and then display them,
such as
the first person's name = InstanceValueIf(the people, the person's name, the person's id = 1)
the first person's name is now a global attribute and can be displayed on global question screens.
Hope this helps!
Ben

CMP and Transaction Attribute

Hi All!
I try to play with cmp entity beans. All I try to do is find instance and call one from the methods.
When I use transaction attribute another than "Required", I get exception 25222. Application module creation exception.
If I change attribute to "Required New" then I get error while bean try to UPDATE record.
I can't understand why this update appear on findByPrimaryKey!
Can any body give some information on JBO behavior?
Mike
null

I do one more test and found
UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

Compound char and transaction data

Hi experts
We have a new characteristic ZCONTRACT.
A few master data datasources delivers this new object with attributes.
ZCONTRACT consists of time dependent attributes and additionaly this field ZOBJ_NO (object number).
ZOBJ_NO is compounded to ZCONTRACT, reason:
ZCONTRACT
ZOBJ_NO
DATETO
DATEFROM
ZOBJ_TY
ZDISCONT
80245202
7000000458
31.12.9999
01.01.1000
1
80245202
7000000460
31.12.9999
01.01.1000
6
80245202
31.12.9999
01.01.2014
2
Characteristic ZDISCONT is time-dependent and has no relation to compounded field ZOBJ_NO.
ZOBJ_TY (object type) is delivered with ZCONTRACT and ZOBJ_NO from one datasource; at this place the valid dates are set constant.
ZOBJ_NO and ZOBJ_TY are non-transactional data relevant, meaning that there is no split or logic in the transactional data including these fields.
The business requirement is to report over ZOBJ_TY.
The idea was to use ZOBJ_TY as active navigational attribute in the infocube.
While assigning ZCONTRACT to the infocube, the compounded field ZOBJ_NO automatically is assigned to the cube.
Now, as there is no logic for this field ZOBJ_NO (and also ZOBJ_TY) in the transactional data, I recognized that it is not possible to solve it through this way.
Do you agree? Are there any other ways to realize this requirement?
Thanks

Hi Thomas,
ok, it get's a bit more complicated.
As I understood 0CML_CASHFLOW only returns ZCONTRACT, but not compounded to ZOBJ_NO. ZDISCONT is part of 0CML_CASHFLOW.
IF you follow the approach above, you have to duplicate your data from 0CML_CASHFLOW to new DSO.
Example:
ZONTRACT ZOBJ_NO 0DATETO ZOBJ_TY
1                  1                 1.1.2013    1
1                  1                  1.1.2014   2
2                  1                  1.1.2013   1
2                  2                  1.1.2014   3
As you said is ZDISCONT time-dpendent.
So data in 0CML_CASHFLOW looks like that
ZCONTRACT   0DATETO ZDISCONT
1                        1.7.2013    1
1                        1.3.2014     2
2                        1.3.2012     1
2                        1.4.2013     2
2                        1.5.2014     3
Now you have to find for each contract the correct validity period from master data and create correpsonding records:
Goal is following records in New DSO, if I understood correctly:
ZCONTRACT   ZOBJ_NO    0DATETO   ZOBJ_TY   ZDISCONT
1                               1          1.1.2013         1              1
1                               1           1.1.2014         2              2
2                               1           1.1.2013         1              2
2                                2          1.1.2014         3              3
For this you need a lookup in the endroutine in transformation from 0CML_CASHFLOW to new DSO which finds for each ZCONTRACT the corresponding ZCONTRACT master data entry and creates the ZDISCONT value in New DSO.
Regards,
Jürgen

Calculation based on display Attribute and Nav attribute

Hi all,
i have a problem in sap biw 3.5 .at query designer level i have issue is
i have master data CHARECTRISTICS OUC_CONTRACT having attributes mvn_date,leg_mvn_date .i need to display union of both dates in single column.
Regards
satish

Your simplest solution is to modify your infoobject and create a new attribute that is the characteristic that you wish to display. Update the transfer rule or DTP with a function that merges the two other attributes into the new attribute, and then use that attribute in your query.
Alternatively you can set these attributes up as Navigational attributes, and then you can manipulate them as independent characteristics in your query results. But this will significantly reduce the performance of your query.

Error to create a new attribute and modify attribute retriever in weblogic

Hi Experts
I have intalled a weblogic server protected by Oracle Entitlements Server, this server contain a web app deployed, this app have policies to restrict the access to resources. For this policies i created an attribute retriever in weblogic console after, i did define an attribute to map this attribute retriever and used in a policy but, I have a problem when i try to create a new attribute or modify an attribute retriever, navigate to Home >Summary of Security Realms >"OES REALM" >Providers >ASIAuthorizationProvider clic on tab "attributes" and appears this errorr:
Error opening /ext_jsp/security/providers/retrievers/CreateALESAttributes.jsp.
The source of this error is:
java.lang.NullPointerException
     at com.bea.retrievers.action.utils.BaseActionUtils.getNonALESAttributeRetrievers(BaseActionUtils.java:370)
     at jsp_servlet._ext_jsp._security._providers._retrievers.__createalesattributes._jspService(__createalesattributes.java:152)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
     at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119)
     at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
     at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:365)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._wlsconsole.__flowlayout._jspService(__flowlayout.java:175)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._wlsconsole.__gridlayout._jspService(__gridlayout.java:219)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._wlsconsole.__twocollayout._jspService(__twocollayout.java:205)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
     at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
     at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
     at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
     at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
     at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
My product versions are:
Weblogic 10.3.2
OES WLS-SSM 10.1.4.3 + CP4
OES Admin 10.1.4.3 + CP4
DB 11gR1
Anybody can help me please.
Regards

You need to add attribute to User Extended Attributes its an configuration object. After changes you need to restart the App / Web server. Only after restart IDM will start storing the value into repository and you can use them as global.<<attr name>>
Thanks
MK

Difference between value attribute and value attribute under Node in contex

I have very basic question..it might be very simple but it is giving me a problem.
I have created one Node name "Input" and value attribute "Input1" under it.
I have just created one more value attribute named "in1" not under any Node.
I have created two input filed in the my view.One first I have mapped the value in properties
to variables "Input.Input1" and on another "in1".
When I deploy and run the application one Input box is coming as readonly and other is working fine .Will anybody tell me why it is so?

There is no major difference between value attribute and inside a node.
It is a separation of attributes. Usually all the attributes belongs to same purpose will create in one value node. Like, calling one BAPI - requestListBAPI - it contains all the bapi related value attributes.
For your question, one field is read only(Input.Input1), bcz that context is not created. see the context properties.....cardinality will be 0..n. Change the cardinality to 1...n (<b>or</b>) create that context element .
In your implementation create that value node like this in your init method.
wdContext.createInputElement();
It will solve your problem.
in1 - is a value attribute, which is mapped to your input element. It wont have any problem.
Regards,
Sri

CMR and Transaction Attribute

I got two ReadOnly CMP entity beans with a 1:N relationship, and one session facade,
all with the TX attribute of NotSupported. When I tried to get the CMR collection
in the session bean, WebLogic 6.1 SP3 threw an EJBException saying the CMR collection
could not be accessed outside a TX context. Only by changing the TX attribute
of the SLSB to Required (left the CMP bean TX attribute unchanged) could I get
the collection. What is the reason behind this behavior? I want the caching
feature of the ReadOnly beans but do not want ot pay any price for transactions.
Is this possible?

I do one more test and found
UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

Serial attribute and org attribute problems with item master

IF i want to unassign an item from an org, how would i do tht
The check is not updateable in the organization assignment tab
Secondly:
When i try to make an existing item serial controlled, i go to inventory tab on item master and when i change the serial control attribute GENERATION then "For some items it says APP-INV-05525: Either On Hand quantity or pending transactions exist for item, cannot change this value"
But for same item if i choose GENERATION sales order issue than it works fine.
Thirdly:
How would i Use generated serial numbers..how to assign them or use them for issuing and recieving

Regarding the 1st part of your query: Unassigning item from an Org
You cannot unassign an item that way (by unchecking the Assigned checkbox).
You have 2 options:
1) Delete the item from the respective Org if it is not yet transacted in that org.
Navigation : Items-> Delete Items
Once selecetd this will open deletion Group screen, please enter a new group name and description and for type select Item from LOV and then in details Tab enter your item that you want to be taken out.
Save the transaction and then click on Delete group button at the bottom of the screen --> this will raise a concurrent request.
If it is already transacted in the respective org from where you want to delete it then system will not allow to delete the item for audit trail purpose.
2) You can make the item 'Inactive' to prevent transactions or ordering (purchasing/sales) you can uncheck the appropriate attributes on that item in the org (assuming your attributes controls allow it at org level rather than master level).
Regarding Serial number generation options a) At Receipt and b) At Sales Order Issue:
a) At Receipt >> Create and assign serial numbers when you receive the item. As you move the material within inventory and until you issue it out you have to use the serial number for those transactions.
b) At Sales Order Issue >> Create and assign serial numbers when you issue (ship) the item against a sales order. For this option serial numbers are required at ship confirm.
Now as per the definitions given above, if there on-hand already exists in your organization(s) then you cannot set the serial generation control "At Receipt". Because in that case all existing on-hands should have serial number assigned which is not the case. On-hand should be zero to set the control "At Receipt". Hence system will prevent you from setting it to "At Receipt" when on-hamd exists. Also in your post you mentioned that you tried to change the control in Item Master, that means serial control generation attribute is set at Master level for you. In this case it will consider on-hands for that item in all the child orgs.
On the other side if you are setting serial control generation "At Sales Order Issue" then seral number is not required for existing on-hands because it will be created and assigned during ship confirm. So system will not prevent even if on-hand exists.
Considering the options available in the system your third question (How would i Use generated serial numbers..how to assign them or use them for issuing and recieving) not very clear. The "generated serial numbers" part is creating little confusion in mind as to what you are actually looking for.
As explained above, if control is set "At Receipt" >> Create and assign serial numbers when you receive the item. Use the Lot/ Serial button on the right hand corner of the material transaction screen and enter the serial number.
If control is At Sales Order Issue >> Create and assign serial numbers when you issue (ship) the item against a sales order. In the Shipping Transaction screen use Tools >> Serial Numbers option before ship confirm and enter the serial number.
But if you have set the control as "Predefined" then, assign predefined serial numbers (by generating before hand) when you receive the item. Thereafter, for any material transaction, you must provide a serial number for each unit.
Hope this helps.

Difference between Navigation attribute and normal attribute

Hi Experts,
What is the use of Navigation attribute in place of normal attribute? When we need to use navigation attribute instead of normal attribute?
Thanks!
Sapna

Hi Sapna,
Please try to search...this has been discussed many many times.

Integrating Business Object Attributes and Database attribute

Newbie using Oracle BPM 11g
I am trying the following:
1)Display two process fields from Business Objects (say firstname, last name) and one field which is a dropdown (say branchcode) from database using ADF UI.
2)Initiator enters the firstname,lastname and then selects a branchcode from the drop down and submits the form.
3)A Reviewer has to view these three fields selected by the Initiator.
My question is how do we enable the reviewer to see the branchcode selected by the Initiator(as it is list of values from database and not from a business object)
Sudip

Hi,
unfortunately this didn't solve it.
The confusing is, that I see the System in the loaded DQE window at the metadata loader, but the corresponding business objects of this system appear without any parameters.
I have no idea what else to do!
christoph

Exclusive attributes and compound attributes

hi
i want to know wat r exclusive attributes ,compound attributes and transitive attributes.

Hi,
Compounding attributes are superior Attributes .
The following link will give you the Compounding Wwith Example :
http://help.sap.com/saphelp_nw70/helpdata/en/6f/c7553bb1c0b562e10000000a11402f/frameset.htm
Transtive Attribute : This is it self is a Display attribute.
Ex :
0EMPLOYEE ( Say as "A")
- > 0EMPNAME (Attr of 0EMPLYOEE) ( Say as "B" )
-> 0EMPDSG ( Attr of 0EMPNAME) ( Say as "C" )
As per the aove example "B" is attribute of "A" and "C" is attribute of "B".There is direct relation between A & B and B& C.Be coz of B is denpendent on "A" C will also have dependent on "A" indirectly.So in this case we will call "C" is Transitive attribute of "A".
Regards
Ram.

Open Hub with Attributes and Texts

Hi,
I´d like to know if it´s possible to have one open hub (database table) with texts and attributes.
There´s no problem when I create it or it´s transformations and DTP´s, but when I try to load texts, after attributes load, it always generates a dump: SAPSQL_ARRAY_INSERT_DUPREC.
I´d like to know a way without using a DSO, any suggestions?!
Kind Regards,
Tomas

Hi,
Pls chk SAP notes system, check SAP note 668466 for some help for this error.
*As according to SAP NOTE ;668466*
Summary
Symptom
You load master data attributes or texts for a characteristic. The loading terminates with runtime errors of the type SAPSQL_ARRAY_INSERT_DUPREC or with error message RSDMD 199. The termination point is in the DBFIRE method of the CL_RSDMD_UPDATE_MASTER_DATA class.
Other terms
Loading master data, attributes, texts, SAPSQL_ARRAY_INSERT_DUPREC, CL_RSDMD_UPDATE_MASTER_DATA, DBFIRE
Reason and Prerequisites
When you load attributes or texts, data records are usually inserted in the master data tables of the characteristic using an array insert statement (P, Q, X, Y, T tables). This results in a SAPSQL_ARRAY_INSERT_DUPREC runtime error if data records that are to be inserted and that relate to the unique primary key of the relevant database table already exist in this table. The following possible reasons are currently known for the occurrence of the SAPSQL_ARRAY_INSERT_DUPREC runtime error:
1. Data inconsistencies in the master data tables of the characteristic
SAPSQL_ARRAY_INSERT_DUPREC runtime errors or RSDMD 199 may occur if the data appears in an inconsistent status in the master data tables of the characteristic before you load attributes or texts. Notes 323140, 566044, 592757 and 599269 describe this (among other things) in more detail.
2. Parallel loading of nondisjunct data packages
If master data attributes are loaded over several dialog processes that are running in parallel, you must guarantee that the data packages of the relevant request are strictly disjunct concerning the characteristic value. This means that all data records that belong to a certain characteristic value may only be contained in a single data package. If data records of a certain characteristic value are distributed over several data packages, this may cause conflicts during the parallel loading of these packages when the master data tables are accessed and this may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors.
The same conditions that apply to loading attributes also apply to loading language-independent master data texts. If language-dependent texts are loaded in parallel, the data packages must be disjunct in relation to the combination of characteristic value and language indicator.
Note 566044 also describes the problematic nature of nondisjunct data packages or duplicate or overlapping data records.
3. Parallel loading of time-dependent attributes or texts
When you load time-dependent attributes or texts, a data record that is to be loaded is assigned to a characteristic value and also specifically to a time interval within which the contained attribute values or texts are valid. For this reason, requests for loading time-dependent attributes or texts typically contain several data records for each characteristic value. If data records of a certain characteristic value or the combination of characteristic value and language indicator are distributed over several data packages, this may (as already explained) cause conflicts when the master data tables are accessed and may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199.
4. Delta update of an ODS object in a characteristic
If you use a delta update from an ODS object to load master data attributes or texts, the activation of the ODS object determines the contents of the data packages that are used for loading the attributes or texts. If all of the ODS loading requests that are used as the data basis for the update into the characteristic are activated together in one step, this guarantees that the system sets up the data packages strictly disjunct in relation to the key fields of the ODS object. If the key fields of the ODS object are displayed one for one on the compounded characteristic value in the update rules, the data may be updated to the characteristic in parallel and by package.
However, if ODS loading requests that were activated at different times appear in the data basis for the update, data records of a certain ODS key or characteristic value may be distributed over several data packages. As already explained, this may cause conflicts when you access master data tables of the characteristic, and it may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199.
This problem is also described in Note 666213.
5. Simultaneous loading of attributes and transaction data
If, when loading attributes of a characteristic, you discover that there are still no entries in the master data tables (P, Q) for a specific characteristic value, the system prepares to insert corresponding data records into these database tables. You can load transaction data into an InfoCube or an ODS object, for example, with the option to create missing master data entries for characteristics that involved during the loading. If a request now creates entries for transaction data in the master data tables (P, Q) of the characteristic before the process has inserted corresponding data records into the master data tables (P, Q) for loading attributes for this characteristic, this may result in a SAPSQL_ARRAY_INSERT_DUPREC runtime error or error message RSDMD 199.
This problem may also occur if you load attributes simultaneously for a characteristic that contains the other characteristic as a navigation attribute or compounding part. If a characteristic is compounded to other characteristics or if it contains characteristics other than the navigation attributes, the system also creates SID values for these dependent characteristics when the attributes are loaded depending on the settings in the InfoPackage.
Solution
To repair a possible inconsistency in the data, implement the RSRV test for master data.
To avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199 when you load master data, carry out the following actions. The actions to be performed in each case depend on which of the above-mentioned reasons is responsible for the runtime error:
1. Data inconsistencies in the master data tables of the characteristic
If data inconsistencies are responsible for the runtime error, you can usually use the tests in transaction RSRV or the RSDMD_CHECKPRG_ALL program to solve this problem. Notes 323140, 566044, 592757 and 599269 describe these (among other things) in more detail. If you cannot implement an automatic correction in this way, you may have to use an ABAP program that is adjusted to the relevant situation to restore the data consistency.
2. Parallel loading of nondisjunct data packages
If the runtime error does not lead back to the parallel loading of nondisjunct data packages, you must identify the duplicate data records that cause the problem. As described in Note 566044, you can change the insertion into master data tables from one array insert to an individual insert statement. If you use a single record insert statement to insert data records, duplicate data records are logged in the monitor by error messages (RSDMD 196). If the data records of a failed request are still available in the PSA, you can also search for duplicate data records directly in the relevant PSA table.
You may also create duplicate data records if key values are changed in the transmission rules or update rules. If relevant rules are defined, you should check these to see if they can possibly create duplicate data records. If this is the case, you must correct the rules accordingly.
3. Parallel loading of time-dependent attributes or texts
The extractors used for loading time-dependent attributes or texts cannot guarantee that all data records assigned to a certain key value are contained together in only one data package. For this reason, to avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199, you should not load time-dependent attributes and texts in parallel. Data packages are processed serially if the 'PSA only' and 'Update Subsequently in Data Targets' settings under 'Processing' are used in the InfoPackage.
4. Delta update of an ODS object in a characteristic
To avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199 during the delta update from an ODS object to a characteristic, you must ensure that the data basis used for the update to the characteristic consists exclusively of ODS loading requests that were activated together in one step only. Note 666213 describes in detail how you can ensure this.
5. Simultaneous loading of attributes and transaction data
If the runtime error occurs because another load task creates SID values or master data for the same characteristic at the same time when attributes are loaded, you can only solve the problem by rescheduling. The load task in question must be scheduled in such a way that you can exclude simultaneous processing.
*pls assign points,if info is useful*
Regards
CSM reddy

Attributes and attribute values for a Product

Hi all
Is there any table or FM from where I can get a list of all the attributes and the attribute values linked to a particular product?
I got tables which link product with Prod Category, Prod Category with Set types and so on.
Could anyoe please provide me an FM which will give the attribute and its values for a particular product?
Please help!!
Regards
Debolina

Attributes created under s settype will be under the table with the name of that particular settype itself i.e Table name and the settype name are the same.
The other part of your question of where to find the list of all settypes and their corresposing attributes, you can make use of COMM_PR_FRG_REL.
Regards,
Harshit

File and boolean attribute on item

Hi,
I work with Oracle9iAS Portal PL/SQL API (9.0.2.6).
I define an item type (CAID = 213/ ID = 37399) with several attributes. When I try to create/modify an item I have problems with boolean attributes and file attributes.
In case of boolean attributes, I'm not able to set the value to true. I try with several values (IS_ON, True, 1) but the attribute is still set to false. Is there anything wrong with the value I assign to the attribute before creating the item ? When I try to create the item and then modifying the attribute, the value stay to false.
For the file attributes, I use the upload_blob function inside wwsbr_api and the file appear in the wwdoc_document table. I set the file attribute value with the return value of the upload_blob function.
When I call the add_item_post_upload, an error occurs (ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException : -29532)
Is this a bug or not ?
Thanks Eddy.
For help see my sample code below :
(ID of attribute, page, region are correct. I also test each type of attribute separately)
declare
l_master NUMBER;
l_store portal.wwsto_api_session;
l_custom_attribute portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_id portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_caid portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_data_type portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_str VARCHAR2(100);
l_Blob BLOB;
l_filename VARCHAR2(100);
begin
-- set context
portal.wwctx_api.SET_CONTEXT('ctx','ctx01','');
-- load a session (Allow use of set_Attribute ...)
DBMS_OUTPUT.put_line('Load session');
l_store := portal.wwsto_api_session.load_session('ctx','ctx');
-- set parameters
-- item type = 'Item_ed'
l_store.set_attribute('ITEM_TYPE', 37399); -- Item type id
l_store.set_attribute('ITEM_CAID', 213); -- Item type caid (page group owner of item type)
l_store.set_attribute('PAGE_GROUP_ID', 213); -- Page group
l_store.set_attribute('FOLDER_ID', 37179); -- Page within page group
l_store.set_attribute('REGION_ID', 3216); -- Region id within page
-- see wwv_user_corners to determine template of page
-- see wwsbr_all_folder_regions for region display_name and region id (for template)
-- Get date format to insert right date string
SELECT DISTINCT value
INTO l_str
FROM v$nls_parameters
WHERE parameter = 'NLS_DATE_FORMAT';
dbms_output.put_line('date format ins : ' || l_str);
-- define attributes (for example, id are hardcoded
DBMS_OUTPUT.put_line('Define attributes');
-- 1080 = PRODUCT_CODE
l_custom_attribute(1) := 'MEHI';
l_custom_attribute_id(1) := 1080;
l_custom_attribute_caid(1) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(1) := 'text';
-- 1081 = PRODUCT_AUTHOR
l_custom_attribute(2) := 'ESTAT';
l_custom_attribute_id(2) := 1081;
l_custom_attribute_caid(2) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(2) := 'text';
-- 1469 = LANGUAGE
l_custom_attribute(3) := 'fr';
l_custom_attribute_id(3) := 1469;
l_custom_attribute_caid(3) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(3) := 'text';
-- 3 = title
l_custom_attribute(4) := 'title value';
l_custom_attribute_id(4) := 3;
l_custom_attribute_caid(4) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(4) := 'text';
-- 50 = wwsbr_text_
l_custom_attribute(5) := 'wwsbr_text_ value';
l_custom_attribute_id(5) := 50;
l_custom_attribute_caid(5) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(5) := 'text';
-- 1464 = Release date
l_custom_attribute(6) := TO_CHAR(TO_DATE('21-JAN-2004 10:00 AM', 'DD-MON-YYYY HH12:MI PM'),l_str);
l_custom_attribute_id(6) := 1464;
l_custom_attribute_caid(6) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(6) := 'date';
-- 1108 = download
l_custom_attribute(7) := 'http://www.oracle.com/';
l_custom_attribute_id(7) := 1108;
l_custom_attribute_caid(7) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(7) := 'url';
-- 1485 = CDROM
l_custom_attribute(8) := '1';
l_custom_attribute_id(8) := 1485;
l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(8) := 'boolean';
-- 1111 = PAGE_NB
l_custom_attribute(8) := '1';
l_custom_attribute_id(8) := 1111;
l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(8) := 'number';
-- 1783 = COVER_IMAGE
-- get image
SELECT BANNER
INTO l_Blob
FROM metadata_tbl
WHERE PRODUCT_CODE = 'caa10000';
-- upload image in repository
l_filename := portal.wwsbr_api.upload_blob('BANNERupload',l_Blob, 'image/pjpeg');
DBMS_OUTPUT.put_line('filename : ' || l_filename);
l_custom_attribute(9) := l_filename;
l_custom_attribute_id(9) := 1783;
l_custom_attribute_caid(9) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(9) := 'file';
DBMS_OUTPUT.put_line('Insert item starts');
l_master := portal.wwsbr_api.add_item_post_upload(
p_caid => l_store.get_attribute_as_number('PAGE_GROUP_ID'),
p_folder_id => l_store.get_attribute_as_number('FOLDER_ID'),
p_display_name => 'Insert : MEHI',
p_type_id => l_store.get_attribute_as_number('ITEM_TYPE'),
p_type_caid => l_store.get_attribute_as_number('ITEM_CAID'),
p_region_id => l_store.get_attribute_as_number('REGION_ID'), --to set or default
p_display_option => portal.WWSBR_API.IN_PLACE,
-- p_category_id in number default general_category,
-- p_category_caid in number default shared_objects,
-- p_perspectives in g_perspectiveidarray default g_perspectiveidemptyarray,
-- p_perspectives_caid in g_caid_array default g_empty_caid_array,
-- p_author in varchar2 default wwctx_api . get_user,
-- p_image_name => l_filename,
-- p_image_alignment in varchar2 default align_left,
-- p_description in varchar2 default null,
-- p_keywords in varchar2 default null,
-- p_file_name =>l_filename, --in varchar2 default null,
p_text => 'text field',
-- p_url in varchar2 default null,
-- p_plsql in varchar2 default null,
-- p_plsql_execute_mode in varchar2 default null,
-- p_plsql_execute_user in varchar2 default null,
-- p_folderlink_id in number default null,
-- p_folderlink_caid in number default null,
-- p_publish_date in varchar2 default null,
-- p_expire_mode in varchar2 default permanent,
-- p_expiration in varchar2 default null,
-- p_master_item_id in number default null,
-- p_hide_in_browse in number default no,
-- p_checkable in number default no,
-- p_parent_item_id in number default 0,
p_attribute_id => l_custom_attribute_id,
p_attribute_caid => l_custom_attribute_caid,
p_attribute_data_type => l_custom_attribute_data_type,
p_attribute_value => l_custom_attribute
DBMS_OUTPUT.put_line('Insert item ends. Item identifier : ' || l_master);
-- Invalidate cache from SQLPLUS
portal.wwpro_api_invalidation.execute_cache_invalidation;
DBMS_OUTPUT.put_line('Cache invalidated');
-- Drop session
portal.wwsto_api_session.drop_session('ctx','ctx');
-- Clean context
portal.wwctx_api.clear_context;
COMMIT;
exception
WHEN portal.wwctx_api.AUTHENTICATION_EXCEPTION THEN
DBMS_OUTPUT.PUT_LINE('AUTHENTICATION_EXCEPTION : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.CANNOT_INSERT_DOCUMENT THEN
DBMS_OUTPUT.PUT_LINE('CANNOT INSERT DOCUMENT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_FOLDER THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_FOLDER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_ID THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_NAME THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_AUDIT THEN
DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_NONE THEN
DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ILS_DISABLED THEN
DBMS_OUTPUT.PUT_LINE('ILS_DISABLED : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ILS_DISABLED_FOR_ITEM THEN
DBMS_OUTPUT.PUT_LINE('ILS_DISABLED_FOR_ITEM : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_CAID THEN
DBMS_OUTPUT.PUT_LINE('INVALID CAID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_CATEGORY THEN
DBMS_OUTPUT.PUT_LINE('INVALID CATEGORY : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE_FORMAT THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE_FORMAT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_NUMBER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_FOLDER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_FOLDER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_FOLDER_ID THEN
DBMS_OUTPUT.PUT_LINE('INVALID FOLDER ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_ITEM_ID THEN
DBMS_OUTPUT.PUT_LINE('INVALID ITEM ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_ITEMTYPE THEN
DBMS_OUTPUT.PUT_LINE('INVALID ITEMTYPE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_MOVE THEN
DBMS_OUTPUT.PUT_LINE('INVALID MOVE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_NAME THEN
DBMS_OUTPUT.PUT_LINE('INVALID NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('INVALID NUMBER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PERSPECTIVE THEN
DBMS_OUTPUT.PUT_LINE('INVALID PERSPECTIVE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PLSQL_EXECUTE_USER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PL/SQL_EXECUTE_USER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_FORMAT THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_FORMAT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_VALUE THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_VALUE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_USERNAME THEN
DBMS_OUTPUT.PUT_LINE('INVALID USERNAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_CREATION_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM_CREATION ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_NOT_FOUND_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM NOT FOUND ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_UPDATE_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM_UPDATE_ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_DISPLAY_NAME THEN
DBMS_OUTPUT.PUT_LINE('MISSING DISPLAY NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_ITEM_TYPE THEN
DBMS_OUTPUT.PUT_LINE('MISSING ITEM TYPE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_NAME THEN
DBMS_OUTPUT.PUT_LINE('MISSING NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_PLSQL_EXECUTE_USER THEN
DBMS_OUTPUT.PUT_LINE('MISSING plsql execute user : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NAME_TOO_LONG THEN
DBMS_OUTPUT.PUT_LINE('name too long : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NO_ITEM_REGION THEN
DBMS_OUTPUT.PUT_LINE('not item region : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NO_MASTER_ITEM_ID THEN
DBMS_OUTPUT.PUT_LINE('no master item id : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NOT_ENOUGH_PRIVS THEN
DBMS_OUTPUT.PUT_LINE('not enough privs : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NULL_EXPIRE_DATE THEN
DBMS_OUTPUT.PUT_LINE('null expire date : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NULL_EXPIRE_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('null expire number : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.PERMISSION_DENIED THEN
DBMS_OUTPUT.PUT_LINE('permission denied : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.PLSQL_REQUIRED THEN
DBMS_OUTPUT.PUT_LINE('plsql required : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.QUOTA_EXCEEDED THEN
DBMS_OUTPUT.PUT_LINE('quota exceeded : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.REQD_ATTR_MISSING THEN
DBMS_OUTPUT.PUT_LINE('reqd attr missing : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.UNKNOWN_ERROR THEN
DBMS_OUTPUT.PUT_LINE('unknown error : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.URL_REQUIRED THEN
DBMS_OUTPUT.PUT_LINE('url required : ' || sqlerrm);
ROLLBACK;
when OTHERS then
DBMS_OUTPUT.PUT_LINE('OTHERS : ' || sqlerrm || ' : ' || sqlcode);
ROLLBACK;
end;

Hi Eddy:
On Friday, we put in a TAR with Oracle support about the identical problem. When editing an item using the API, the boolean attributes always reset. The values of the boolean attributes aren't even being changed. The only reason we need to set them again is the limitation of the API where you have to feed all attributes back in.
So far, Oracle has said it sounds like a bug and they want to know the exact sequence of steps to repeat it.
Rgds/Mark M.
Portal 9.0.2.6

Compound attribute and transactional attribute

Similar Messages

Maybe you are looking for