Printig documents with attributes

Printing documents with attributes
We are using word files for documentation within the solution manager. While printing such documents all attribute information will not be printed.
Does anybody know how to add to the printout the attributes like:
Title, Technical Name, Documentation Type, Status, Priority, Person Responsible, etc.
During the normal printing such information will be not on the paper.

A solution!
It turns out the problem in my case was in fact Suitcase. Previously, I'd tried turning it off, but that didn't fix the problem, so this time, I uninstalled it completely and the problem disappeared. I then began re-adding it (installed 15.0.1, upgraded it, etc.) and the problem resurfaced with the addition of the Photoshop-specific plugin. Deleting that plugin solved the problem. So it seems that "disabling" Suitcase by stopping the TypeCore doesn't seem to actually disable all of the tentacles it sticks into your system.
You can find the plugin here: Applications / Adobe Photoshop CS6 / Plug-ins / Automate / ExtensisFontManagementPSCS6.plugin
(After a restart, I also had to delete the font cache, as described here http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html but your mileage may vary.)
Alternately, if you don't want to delete the plugin, disabling it from within Photoshop seems to work as well. To do that, go to File > Automate > Extensis, click Preferences..., then deselect Enable Suitcase Fusion 4 Auto-Activation.
Fortunately, the plugin doesn't seem necessary at all to use the the core functionality of Suitcase (enabling and disabling fonts) in Photoshop. I didn't even know what these app-specific plugins did until researching this problem, and I still don't quite understand the point of them. I guess they allow you to let the apps for which they're installed do a little bit more of their own management (enable a font via Suitcase that isn't enabled system-wide), but that seems like more control than I need--if I'm enabling a font, I want all my software to be able to use it.
Anyway, the problem seems to be completely solved on my system now, though I just did all this, so more testing over the next few days is required. I'll post here if any issues crop up. I'm interested in hearing if this solves it for anyone else as well.

Similar Messages

Create document with Compound Attributes

Hi, does anyone can solve my problem
I have created a customer parser to parse my customised document say "XXX.PO". I followed the instruction in the developer guide (create customised parser). Everything is fine except the compound attributes, i don't know how to handle the compound attributes in java code. the following is my document definition.
//po detail
<?xml version = '1.0' standalone = 'yes'?>
<ClassObject>
<Name>PoDetail</Name>
<Description>Po attribute definition</Description>
<Superclass Reftype = "name">ApplicationObject</Superclass>
<Attributes>
<Attribute>
<Name>TagName</Name>
<DataType>String</DataType>
<DataLength>80</DataLength>
</Attribute>
<Attribute>
<Name>TagValue</Name>
<DataType>String</DataType>
<DataLength>4000</DataLength>
</Attribute>
</Attributes>
</ClassObject>
//class domain
<?xml version="1.0" standalone="yes"?>
<ClassDomain>
<Name>DocumentDetailDomain</Name>
<DomainType>1</DomainType>
<Classes>
<ArrayElement reftype="name">PoDetail</ArrayElement>
</Classes>
</ClassDomain>
//Document definitaion
<?xml version= '1.0' standalone = 'yes' ?>
<ClassObject>
<Name>PoDocument</Name>
<Description>PoDocument </Description>
<Superclass Reftype = "name">Document</Superclass>
<Attributes>
<Attribute>
<Name>PoNumber</Name>
<DataType>String</DataType>
<DataLength>50</DataLength>
</Attribute>
<Attribute>
<Name>ItemDetail</Name>
<DataType>PublicObject</DataType>
<ClassDomain RefType="name">DocumentDetailDomain</ClassDomain>
</Attribute>
</Attributes>
</ClassObject>
Does anyone can show me how to handle compound attributes
Many thanks
Ernest
null

Dear Dmitry Rassakhatsky
Can you please elaborate what you are trying to achive using BAPI_DOCUMENT_CREATE02 and SAP XI.
We would be in better position to suggest solution.
Also most of us will not be able to understand Technical ABAP so request you to provide detail scenario.
With Warm Regards
Mangesh Pande

Error while creating document with attachment.

Hi,
I am getting an error "An error occured while creating the original attribute for PDF"
I tried with out file attachment, it works as you know it is simple....
I tried with various types of attachments like .TXT and .WRD (changed both wsapplication and docfile parameters), however i get the same error. I tried both from presentation and application server (by providing   pf_ftp_dest                = 'SAPFTPA'    pf_http_dest               = 'SAPHTTPA' )
Any idea on how to solve this?
All i need is create a DMS document with a PDF attachment from application server. Are there any other ways to solve this issue?
ws_docdata-documenttype = 'ARE'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CR'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = 'C:\CAD Integ BAPIS_46.pdf'.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
     documentdata               = ws_docdata
IMPORTING
     return                     = v_ret
TABLES
     documentfiles              = it_files   .
BREAK-POINT.
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

Hi,
I found that it is due to document type = 'ARE'. I changed hte document type to one of hte standard type 'TST'. It works for presentation server, but does not work for application server. Any ideas? Any help is appreciated with points.
ws_docdata-documenttype = 'TST'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CT'.
ws_docdata-documentnumber = 'ZNG-10000000017'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = p_file.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
    documentdata               = ws_docdata
   pf_ftp_dest                = 'SAPFTPA'
   pf_http_dest               = 'SAPHTTPA'
IMPORTING
   documentnumber             = v_docnum
   documentpart               = v_docpart
   documentversion            = v_docver
   return                     = v_ret
TABLES
   documentfiles              = it_files   .
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

XML Schema Collection (SQL Server 2012): Complex Schema Collection with Attribute - Should xs or xsd be used in the coding?

Hi all,
I just got a copy of the book "Pro SQL Server 2008 XML" written by Michael Coles (published by Apress) and try to learn the XML Schema Collection in my SQL Server 2012 Management Studio (SSMS2012). I studied Chapter 4 XML Collection of the book
and executed the following code of Listing 4-8 Complex Schema with Attribute:
-- Pro SQL Server 2008 XML by Michael Coles (Apress)
-- Listing04-08.sql Complex XML Schema with Attribute
-- shcColes04-08.sql saved in C:\\Documents\XML_SQL_Server2008_code_Coles_Apress
-- 6 April 2015 8:00 PM
CREATE XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute
AS
N'<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
<xs:complexType>
<xs:sequence>
<xs:element name="name" />
<xs:element name="color" />
<xs:group ref="id-price" />
<xs:group ref="size-group" />
</xs:sequence>
<xs:attribute name="id" />
<xs:attribute name="number" />
</xs:complexType>
</xs:element>
<xs:group name="id-price">
<xs:choice>
<xs:element name="list-price" />
<xs:element name="standard-cost" />
</xs:choice>
</xs:group>
<xs:group name="size-group">
<xs:sequence>
<xs:element name="size" />
<xs:element name="unit-of-measure" />
</xs:sequence>
</xs:group>
</xs:schema>';
GO
DECLARE @x XML (dbo.ComplexTestSchemaCollection_attribute);
SET @x = N'<?xml version="1.0"?>
<item id="749" number="BK-R93R-62">
<name>Road-150 Red, 62</name>
<color>Red</color>
<list-price>3578.27</list-price>
<size>62</size>
<unit-of-measure>CM</unit-of-measure>
</item>';
SELECT @x;
GO
DROP XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute;
It worked nicely. But, I just found out the coding that was downloaded from the website of Apress and I just executed was different from the coding of Listing 4-8 listed in the book: all the <xs: ....> and </xs: ..> in my SSMS2012 are
listed as <xsd:...> and </xsd:...> respectively in the book!!?? The same thing happens in the Listing 4-3 Simple XML Schema, Listing 4-5 XML Schema and Valid XML Document with Comple Type Definition, Listion 4-6 XML Schema and XML
Document Document with Complex Type Using <sequence> and <choice>, and Listing 4-7 Complex XML Schema and XML Document with Model Group Definition (I executed last week) too. I wonder: should xs or xsd be used in the XML
Schema Collection of SSMS2012? Please kindly help, clarify this matter and explain the diffirence of using xs and xsd for me.
Thanks in advance,
Scott Chang

Hi Scott,
Using xs or xsd depends on how you declare the namespace prefix.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
I've posted a very good link in your last question, just in case you might have missed it, please see the below link.
Understanding XML Namespaces
In an XML document we use a namespace prefix to qualify the local names of both elements and attributes . A prefix is really just an abbreviation for the namespace identifier (URI), which is typically quite long. The prefix is first mapped to a namespace
identifier through a namespace declaration. The syntax for a namespace declaration is:
xmlns:<prefix>='<namespace identifier>'
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

Updating a document with category metadata using updateDocument(): error!

I have studied the sample code and the API docs, and I feel pretty sure I am coding it according to the docs, but I cannot successfully update a document with category metadata. I always get a MetaDataSchemaInvalid exception.
My process goes like this:
1. Upload a new file, creating a new document publicobject.
2. Create a CATEGORY_DEFINITION with all the metadata name/value pairs I wish to write.
3. Call FileManager.updateDocument() with this CATEGORY_DEFINITION.
My process differs from the docs in that I am first uploading the document, and then adding the metadata as a second step. I want to get it working this way to make my system more modular. I do not want to make my upload method dependent upon metadata attributes, and vice versa.
Step 1 is working fine. The document is being uploaded to the right folder. Good to go.
Step 3 is where I get the error. If the error is my fault, then it must be a result of what I do in step 2. The structure of my CATEGORY_DEFINITION must be messed up.
Here is my code for creating the CATEGORY_DEFINITION. The Document class is my own entity that encapsulates the binary data for a document, as well as the metadata attributes that are to be assigned to the document once it is uploaded into Content Services. We don't need to worry about where the data comes from. Just assume the raw data is correct.
public NamedValue[] newCategoryAttributeDefinition(Document document, String categoryDisplayName) throws WebserviceClientException {
/* Get the category attribute name-value pairs as a 2-D array. */
Map metadataMap = document.getMetadataParser().getAttributeNameMapping();
List categoryDefinitionAttributeList = new ArrayList();
for(Iterator i = metadataMap.entrySet().iterator(); i.hasNext();) {
Map.Entry entry = (Map.Entry)i.next();
String name = "CUSTOM_" + (String)entry.getKey();
Object value = entry.getValue();
if(value != null) {
categoryDefinitionAttributeList.add(new Object[] { name, value });
Object[][] categoryDefinitionAttributeArray = new Object[categoryDefinitionAttributeList.size()][];
int index = 0;
for(Iterator i = categoryDefinitionAttributeList.iterator(); i.hasNext();) {
Object[] value = (Object[])i.next();
categoryDefinitionAttributeArray[index++] = value;
/* Create the NamedValue tree that describes this category's attribute values. */
Long categoryId = new Long(getCategoryClassId(categoryDisplayName));
NamedValue[] categoryAttributeDefinition = WebserviceUtils.newNamedValueArray(new Object[][] {
{ Options.CATEGORY_ID, categoryId },
{ Options.CATEGORY_DEFINITION_ATTRIBUTES, WebserviceUtils.newNamedValueArray(categoryDefinitionAttributeArray) }
NamedValue[] categoryDefinition = WebserviceUtils.newNamedValueArray(Options.CATEGORY_DEFINITION, categoryAttributeDefinition);
return categoryDefinition;
And below is the resulting CATEGORY_DEFINITION, as seen in a jdb debugger.
-- The OPT.CATEGORY_ID value is equal to the ID column in ODMV_SCHEMACATEGORY, otherwise known as the category class id.
-- My OPT.CATEGORY_DEFINITION_ATTRIBUTES tree for this document has the 4 attributes that I want to set. The category has more than these 4 attributes; I am not populating every attribute. None of the attributes are required, and all are editable. I don't need to include every attribute in my CATEGORY_DEFINITION, even if the values are null, do I? Also, all the attribute names start with "CUSTOM_", which I believe is necessary - right?
-- I am setting only the OPT.CATEGORY_ID and OPT.CATEGORY_DEFINITION_ATTRIBUTES. Am I missing some other required attribute?
http-8888-Processor5[1] http-8888-Processor5[1] dump categoryDefinition
categoryDefinition = {
instance of oracle.ifs.fdk.NamedValue(id=2562)
http-8888-Processor5[1] dump categoryDefinition[0]
categoryDefinition[0] = {
name: "OPT.CATEGORY_DEFINITION"
value: instance of oracle.ifs.fdk.NamedValue[2] (id=2559)
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[0]
categoryDefinition[0].value[0] = {
name: "OPT.CATEGORY_ID"
value: instance of java.lang.Long(id=2558)
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[0].value.toString()
categoryDefinition[0].value[0].value.toString() = "60068"
http-8888-Processor5[1] dump categoryDefinition[0].value[1]
categoryDefinition[0].value[1] = {
name: "OPT.CATEGORY_DEFINITION_ATTRIBUTES"
value: instance of oracle.ifs.fdk.NamedValue[4] (id=2570)
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[1].value[0]
categoryDefinition[0].value[1].value[0] = {
name: "CUSTOM_From"
value: "SA"
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[1].value[1]
categoryDefinition[0].value[1].value[1] = {
name: "CUSTOM_Footer Number"
value: "PRM 34-318"
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[1].value[2]
categoryDefinition[0].value[1].value[2] = {
name: "CUSTOM_To"
value: "PROJECT TEAM"
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
http-8888-Processor5[1] dump categoryDefinition[0].value[1].value[3]
categoryDefinition[0].value[1].value[3] = {
name: "CUSTOM_Subject"
value: "Riverside Energy Resource Center Meeting Minutes-Internal"
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2564)
class$oracle$ifs$fdk$NamedValue: instance of java.lang.Class(reflected class=oracle.ifs.fdk.NamedValue, id=1975)
After building this CATEGORY_DEFINITION, I go on to attempt an update to the document with this information. Here is the method I call. I always fall into the catch(), and the error dump follows the code snippet. Unfortunately, the error doesn't tell me a lot about what's wrong. That's why I am asking for help in spotting any conspicuous errors in my CATEGORY_DEFINITION.
public Item addCategoryToDocument(Item documentItem,
NamedValue[] categoryDefinition)
throws WebserviceClientException {
FileManager fileManager = getWebserviceClient().getFileManager();
Item documentItemWithCategory = null;
try {
documentItemWithCategory = fileManager.updateDocument(documentItem.getId(), categoryDefinition, null);
} catch(Exception e) {
throw new WebserviceClientException("Could not update document with category definition.", e);
return documentItemWithCategory;
http-8888-Processor4[1] http-8888-Processor4[1] dump e
e = {
detailedErrorCode: "ORACLE.FDK.AggregateError"
errorCode: "ORACLE.FDK.AggregateError"
exceptionEntries: instance of oracle.ifs.fdk.FdkExceptionEntry[1] (id=2691)
info: null
serverStackTraceId: ""
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2694)
class$oracle$ifs$fdk$FdkException: instance of java.lang.Class(reflected class=oracle.ifs.fdk.FdkException, id=1972)
org.apache.axis.AxisFault.log: instance of org.apache.commons.logging.impl.Log4JLogger(id=2695)
org.apache.axis.AxisFault.faultCode: instance of javax.xml.namespace.QName(id=2696)
org.apache.axis.AxisFault.faultSubCode: null
org.apache.axis.AxisFault.faultString: "ORACLE.FDK.AggregateError:ORACLE.FDK.AggregateError"
org.apache.axis.AxisFault.faultActor: null
org.apache.axis.AxisFault.faultDetails: instance of java.util.Vector(id=2698)
org.apache.axis.AxisFault.faultNode: null
org.apache.axis.AxisFault.faultHeaders: null
org.apache.axis.AxisFault.class$org$apache$axis$AxisFault: instance of java.lang.Class(reflected class=org.apache.axis.AxisFault, id=1928)
java.rmi.RemoteException.serialVersionUID: -5148567311918794206
java.rmi.RemoteException.detail: null
java.lang.Exception.serialVersionUID: -3387516993124229948
java.lang.Throwable.serialVersionUID: -3042686055658047285
java.lang.Throwable.detailMessage: null
java.lang.Throwable.cause: null
java.lang.Throwable.stackTrace: instance of java.lang.StackTraceElement[76] (id=2699)
http-8888-Processor4[1] dump e.exceptionEntries[0]
e.exceptionEntries[0] = {
detailedErrorCode: "ORACLE.FDK.MetadataSchemaInvalid"
errorCode: "ORACLE.FDK.MetaDataError"
id: 348018
info: null
serverStackTraceId: ""
__equalsCalc: null
__hashCodeCalc: false
typeDesc: instance of org.apache.axis.description.TypeDesc(id=2705)
class$oracle$ifs$fdk$FdkExceptionEntry: instance of java.lang.Class(reflected class=oracle.ifs.fdk.FdkExceptionEntry, id=1973)
}

1 – For an existing document, how do I determine what category instances have been applied to it and their attribute values
FdkSession session = …;
// Consider we have an existing item myDoc of type document
Item myDoc = …;
CommonManager cm = Managers.getCommonManager(session);
AttributeRequest[] requestedAttributes = new AttributeRequest[]
// The Categories associated with this Document, if any
new AttributeRequest(Attributes.CATEGORIES,
// sub attributerequest
new AttributeRequest[] {
    // the actual attributes name/values for the category instance – returns a namedvalue array
    new AttributeRequest(Attributes.CUSTOM_ALL,null),
    // the actual category class for the category instance – returns an item
    new AttributeRequest(Attributes.CATEGORY_CLASS_OBJECT,null)
myDoc = cm.getItem(myDoc.getId(), requestedAttributes);
log(myDoc); /* output could look like:
(Item) 14385 DOCUMENT sample3.doc
requested attributes ...
CATEGORIES (Item[])=
(Item) 14387 CATEGORY
requested attributes ...
CUSTOM_ALL (NamedValue[])=
CUSTOM_14352=true (Boolean)
CUSTOM_14353=Internal Only Pending Review (String)
CATEGORY_CLASS_OBJECT (Item)=
(Item) 14354 CATEGORY_CLASS 5044-14351
This means, that for document sample3.doc, we have 1 instance of a category object applied to it.
The category object instance has id 14387. The instance is of a category class object type 14354. The instance has two attributes with internal names CUSTOM_14352, and CUSTOM_15353. The values of these attributes are of type Boolean and String respectively.
2 - How do I update an attribute value of an existing category instance applied to an item
FdkSession session = …;
// Consider we have an existing item myDoc of type document
Item myDoc = …;
.. perform code along the lines of that shown in step1 above to determine existing category instance info on the document ..
FileManager fm = Managers.getFileManager(session);
NamedValue[] categoryInstanceAttributes = new NamedValue[] {
// use the internal attribute name for all attributes
new NamedValue("CUSTOM_14352", Boolean.FALSE),
new NamedValue("CUSTOM_14352", "Company Confidential")
NamedValue[] categoryDef = new NamedValue[] {
// the category instance that we are updating
new NamedValue(Options.UPDATE_CATEGORY_ID,new Long(14387)),
// the updated values of the category instance
new NamedValue(Options.CATEGORY_DEFINITION_ATTRIBUTES, categoryInstanceAttributes)
NamedValue[] documentDef = new NamedValue[] {
new NamedValue(Options.CATEGORY_DEFINITION, categoryDef)
requestedAttributes = ...
myDoc = fm.updateDocument(myDoc.getId(),documentDef,requestedAttributes) ;
3 – For a document item X, what is the associated category configuration which could include
a) what are the category objects I can apply on it (either explicitly restricted by way of ALLOWED_CATEGORIES on the folder configuration, or any site/domain category by way of ALLOW_ALL_CATEGORIES)
b) is there any attribute overrides
c) is there any enforced categories
FdkSession session = …;
// Consider we have an existing item myDoc of type document
Item myDoc = …;
CommonManager cm = Managers.getCommonManager(session);
AttributeRequest[] categoryObjectAttributes = new AttributeRequest[]
// What is the category object class name
new AttributeRequest(Attributes.CLASS_NAME,null),
// What is the category classobject display name
new AttributeRequest(Attributes.DISPLAY_NAME,null),
// get attributes inherited and introduced by category object
new AttributeRequest(Attributes.METADATA_ATTRIBUTES,
new AttributeRequest[]
    // Attribute internal name
    new AttributeRequest(Attributes.ATTRIBUTE_NAME,null),
    // Attribute display name
    new AttributeRequest(Attributes.DISPLAY_NAME,null),
    new AttributeRequest(Attributes.ATTRIBUTE_TYPE,null),
    new AttributeRequest(Attributes.ATTRIBUTE_DEFAULT,null),
    new AttributeRequest(Attributes.ATTRIBUTE_ENUMERATION,null),
    new AttributeRequest(Attributes.ATTRIBUTE_REQUIRED,null),
    new AttributeRequest(Attributes.ATTRIBUTE_SETTABLE,null),
    new AttributeRequest(Attributes.ATTRIBUTE_UPDATEABLE,null),
    new AttributeRequest(Attributes.ATTRIBUTE_HIDDEN,null),
    new AttributeRequest(Attributes.ATTRIBUTE_PROMPTED,null),
    new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDEABLE,null),
AttributeRequest[] overrideAttributes = new AttributeRequest[]
// id of the attribute to be overridden
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_ATTRIBUTE,null),
// id of the category class object to which this attribute override applies
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_CATEGORY_CLASS,null),
// new default value
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_DEFAULT,null),
// should attribute now be prompted
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_PROMPT,null),
// is the attribute now required
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_REQUIRED,null),
// can instances of this attribute have there value updated
new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDE_SETTABLE,null),
AttributeRequest[] requestedAttributes = new AttributeRequest[]
// what is the category configuration for the item
new AttributeRequest(Attributes.CATEGORY_CONFIGURATION,
new AttributeRequest[]
    // Is the category configuration enabled
     new AttributeRequest(Attributes.CONFIGURATION_ENABLED,null),
     // Can the category configuration be overridden or is it final
    new AttributeRequest(Attributes.CONFIGURATION_FINAL,null),
    // What are the required categories for the category configuration and associated attribute information
    new AttributeRequest(Attributes.REQUIRED_CATEGORIES,categoryObjectAttributes),
    // Can any categories in the site be utilized
    new AttributeRequest(Attributes.ALLOW_ALL_CATEGORIES,null),
    // or .. are we restricting the categories to only the following
    new AttributeRequest(Attributes.ALLOWED_CATEGORIES,categoryObjectAttributes),
    // are there any attribute overrides on category object attributes for this category config?
    new AttributeRequest(Attributes.ATTRIBUTE_OVERRIDES,overrideAttributes)
log(cm.getItem(myDoc.getId(), requestedAttributes); /*
If ALLOW_ALL_CATEGORIES is set to true, any category in the domain can be utilized that is not abstract. To determine these, the domain item has a property CATEGORY_CLASSES that returns all category objects in the domain. It also has a property ROOT_CATEGORY_CLASSES which returns just the top level categories (those that have no custom category superclass). You would create a sub AttributeRequest[] checking for CLASS_ABSTRACT when requesting the appropriate categories attribute from the domain.
If ALLOW_ALL_CATEGORIES is set to false, the applicable categories objects that can be utilized on items contained in the folder is determined by the items contained in the ALLOWED_CATEGORIES attribute of the category configuration.
Finally, the REQUIRED_CATEGORIES attribute list the category items that must be applied to all new items added to the folder.
4 – How do I manually apply an instance of a category to an existing item
FdkSession session = …;
// Consider we have an existing item myDoc of type document
Item myDoc = …;
.. use techniques in step3 above to determine what category objects that you planning to apply to the document ..
.. if the category configuration on the item has ALLOW_ALL_CATEGORIES set to true, you can use any category in the system
.. otherwise, you must use a category defined in the allowed categories list
.. the code here is essentially the same as step2 above
.. you must utilize internal attribute names, and specify the id of the category class object
FileManager fm = Managers.getFileManager(session);
NamedValue[] categoryInstanceAttributes = new NamedValue[] {
// use the internal attribute name for all attributes
new NamedValue("CUSTOM_14352", Boolean.FALSE),
new NamedValue("CUSTOM_14352", "Company Confidential")
NamedValue[] categoryDef = new NamedValue[] {
// the id of the category object class for which this new category will be an instance of
new NamedValue(Options.CATEGORY_CLASS_ID,new Long(14354)),
// the updated values of the category instance
new NamedValue(Options.CATEGORY_DEFINITION_ATTRIBUTES, categoryInstanceAttributes)
NamedValue[] documentDef = new NamedValue[] {
new NamedValue(Options.CATEGORY_DEFINITION, categoryDef)
requestedAttributes = ...
myDoc = fm.updateDocument(myDoc.getId(),documentDef,requestedAttributes);
// Note – it is possible for one to peform creation, updating, and deletion of various category instances for an existing item in the fileManager updateDocument call!
// you simply supply multiple Options.CATEGORY_DEFINITIONs to the fm.updateDocument call along with any Options.REMOVE_CATEGORY_IDs 5 – How do I specify a category instance when creating a new item
FdkSession session = …;
.. use techniques in step3 above to determine what category objects that you planning to apply to the new document ..
.. you get the category configuration information from the destination folder!!!
Item destinationFolder = …;
CommonManager cm = Managers.getCommonManager(session);
AttributeRequest[] requestedAttributes = new AttributeRequest[]
// what is the category configuration for the item
new AttributeRequest(Attributes.CATEGORY_CONFIGURATION,
destinationFolder = cm.getItem(destinationFolder.getId(),requestedAttributes);.. if the category configuration on the folder item has ALLOW_ALL_CATEGORIES set to true, you can use any category in the system
.. otherwise, you must use a category defined in the allowed categories list
.. the code here is essentially the same as step2 above, just we are using createDocument and document definitions now
.. you must utilize internal attribute names, and specify the id of the category class object
FileManager fm = Managers.getFileManager(session);
NamedValue[] categoryInstanceAttributes = new NamedValue[] {
// use the internal attribute name for all attributes
new NamedValue("CUSTOM_14352", Boolean.FALSE),
new NamedValue("CUSTOM_14352", "Company Confidential")
NamedValue[] categoryDef = new NamedValue[] {
// the id of the category object class for which this new category will be an instance of
new NamedValue(Options.CATEGORY_CLASS_ID,new Long(14354)),
// the attribute values for this new category instance
new NamedValue(Options.CATEGORY_DEFINITION_ATTRIBUTES, categoryInstanceAttributes)
String destinationFile = "sample.doc";
requestedAttributes = new AttributeRequest[]
new AttributeRequest(Attributes.URL,null)
Item docDef = fm.createDocumentDefinition(new NamedValue[]
new NamedValue(Attributes.NAME, destinationFile),
},requestedAttributes);
String defURL = ... // get URL from document definition
doFileUpload(...) // upload file using http put to defURL
NamedValue[] documentDef = new NamedValue[] {
new NamedValue(Options.USE_SAVED_DEFINITION,new Long(docDef.getId())),
new NamedValue(Options.DESTFOLDER, new Long(destinationFolder.getId())),
// specify character set if appropriate
new NamedValue(Attributes.DOCUMENT_CHARACTER_SET,"ISO-8859-1"),
// specify language if appropriate
new NamedValue(Attributes.DOCUMENT_LANGUAGE,"ENGLISH"),
// apply category instance information
new NamedValue(Options.CATEGORY_DEFINITION, categoryDef),
requestedAttributes = ...
Item doc = fm.createDocument(documentDef,null, requestedAttributes);
// Note – it is possible for one to peform creation of multiple category instances on a document at the same time
// you simply supply multiple Options.CATEGORY_DEFINITIONs to the fm.createDocument call
// Note – that if a folder has a category configuration containing required categories, and you do not specify
// all applicable category definitions on createDocument, you will receive an FdkException along the lines of
// missing metadata. You can catch this exception, and retry the createDocument call supplying the valid category definition(s).

Change Default Document Size Attribute

I understand that I can make a custom attribute that displays the size in KB, MB, etc -
But I want to know how to edit the default Document Size attribute - surely that is possible?

@Steve – you are totally clear what you are doing and what you like to do.
But I fear an automatic setting that is creating the page size according to an asset's size does not exist right now.
I can change the size of a new document beforehand, if no document is open and create a new size in the document's properties dialog with the keyboard shortcut alt + cmd + p (in my German InDesign on Mac OSX 10.7.5). But you have to know in advance what size that should be.
Example: If I chose A3 instead of A4 (my default) when no document is open and double click an asset in a CC Library the asset will be placed in a one page document sized A3.
1. Changing the size (no document is open) in my German UI of InDesign CC-2014.2:
2. Double click and the result is according to the settings I made:
Uwe

XSLT bug with attributes+in memory DOM

Hello,
I know there was a thread about this one some time ago but i
don't know the current state of this matter, so :
The XSLT processor has problems with attributes when the DOM was
build dynamically (attributes are returned as being empty). When
i save the same DOM, reload it and then do the transform
attributes are properly transformed.
The Version 2.0.0.1 of the Java parser states to have solved a
problem when accessing attributes (bug #920536) but this seems to
be an other one (i tried 2.0.0.0 and 2.0.0.1 and both had this
problem).
Bye Heiko.
null

We were unable to reproduce the problem you illustrated. We got
the output:
<HTML>
<BODY>
the value is : 1
</BODY>
</HTML>
irrespective of whether the lines were commented out. Can you
describe your environment - JRE/JDK, OS. etc?
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
You wrote:
: Hello,
: the following program illustrates what i mean :
: package testing;
: import oracle.xml.parser.v2.*;
: import org.w3c.dom.*;
: import java.io.*;
: public class XMLTest {
: public static final void main(String [] args) throws
: Exception {
: XMLDocument doc=new XMLDocument();
: doc.setVersion("1.0");
: doc.setStandalone("yes");
: Node root=doc.createElement("ROOT");
: Node att=doc.createAttribute("value");
: att.setNodeValue("1");
: root.getAttributes().setNamedItem(att);
: doc.appendChild(root);
: doc.print(new FileOutputStream("c:\\test.xml"));
: DOMParser parser=new DOMParser();
: parser.parse(new FileInputStream("c:\\test.xml"));
: doc=parser.getDocument();
: XSLStylesheet xsl=new XSLStylesheet(new
: FileInputStream("c:\\test.xsl"), null);
: XMLDocument out=new XMLDocument();
: out.appendChild(new XSLProcessor().processXSL(xsl,
doc));
: out.print(System.out);
: with the stylesheet test.xsl as follows :
: <?xml version="1.0"?>
: <xsl:stylesheet
: xmlns:xsl="http://www.w3.org/XSL/Transform/1.0"
: xmlns="http://www.w3.org/Profiles/xhtml1-transitional"
: default-space="strip"
: indent-result="yes"
: >
: <xsl:template match="ROOT">
: <HTML>
: <BODY>
: the value is : <xsl:value-of select="@value"/>
: </BODY>
: </HTML>
: </xsl:template>
: </xsl:stylesheet>
: if you run the program as given the result is :
: the value is:
: but when you uncomment the lines storing & retrieving the
: document the result is as i would expect it :
: the value is: 1
: Bye Heiko.
null

How to attach a document with the Requisition Workflow?

I am testing the Oracle Requisition Demo workflow.Whenever i initiate the
workflow process with Reminder Requisition Document Option.The browser pop up
with the Error "The requested URL cannot be retrieved". Can anyone please guide me how do i attach a document with this process?
Regards,
Abrar

This field in the demo is designed to execute a PL/SQL procedure not store and attached document.
for example if you launch it from the demonstration Page instead of the launch process page the following will be populated into the document field. (PLSQL:WF_REQDEMO.REMINDER_REQ_DOCUMENT/WFDEMO:A1)
You can store a CLOB or BLOB in a workflow document attribute. Here is a link to the doc.
http://download-west.oracle.com/docs/cd/B13789_01/workflow.101/b10284/defcom11.htm#doc
If you want to upload and pass documents through a workflow you can do it in a variety of ways. Personally I would use Oracle Files if I wanted it off the shelf. Or use Oracle Text and the database and pass the document throught the workflow as a URL. There is also the CMSDK.

Adobe Reader v10.4.4 support for PDF with attributes

Hi there,
I recently downloaded Adobe Reader v10.4.4 for my iPhone. I was just wondering if it supports PDFs with attributes?
To test I created two PDFs using GIS application called MapInfo Professional:
1. PDF without attributes - this one was able to open succesfully
2. PDF with attributes - this one could not open and threw an error "Not a valid PDF document"
Any help appreciated.
Thanks,
Dave

Hi Steve,
Thanks for your speedy reply. Yes, I forgot to mention, these PDFs can open up in my desktop version of Adobe Reader (v8) for Windows.
PDF with attributes means that there is records (attribute data) contained in the PDF which is being saved into the PDF when it was created using the GIS application. For example if looking at postal area: PDF map, ID number, place name, population, area (sq m) values etc.
The specific tool/function which allows these attribute values to be exposed is called the 'Object Data' tool (under Tools > Object Data in the desktop version)
(I have attached a screenshot showing these attributes in the desktop version so you may get a better understanding hopefully! Pls see link below)
http://i296.photobucket.com/albums/mm199/dkny1315/ScreenHunter_44Feb151332_zpsd515b1af.gif
If you need any further info or details, please let me know
Thanks,
Dave

How to parse an XML document with oracle8i

Has anyone a good link or an example how to decode and store an XML document into an oracle8i database.
I' ve found only good things for oracle9i.
Thank you
Roger

Here is an example of parsing xml taken fro Oracle8i 8.1.7 xdk.
This one uses external OS files to pase, but could be easily converted to
use CLOB or VARCHAR2 string for parsing XML documents.
IF you wanted to use CLOB to store and manipulate xml documents you can use XMLParser and XMLDom
packages along with the DBMS_LOB package to do that.
-- This file demonstates a simple use of the parser and DOM API.
-- The XML file that is given to the application is parsed and the
-- elements and attributes in the document are printed.
-- The use of setting the parser options is demonstrated.
set serveroutput on;
create or replace procedure domsample(dir varchar2, inpfile varchar2,
errfile varchar2) is
p xmlparser.parser;
doc xmldom.DOMDocument;
-- prints elements in a document
procedure printElements(doc xmldom.DOMDocument) is
nl xmldom.DOMNodeList;
len number;
n xmldom.DOMNode;
begin
-- get all elements
nl := xmldom.getElementsByTagName(doc, '*');
len := xmldom.getLength(nl);
-- loop through elements
for i in 0..len-1 loop
n := xmldom.item(nl, i);
dbms_output.put(xmldom.getNodeName(n) || ' ');
end loop;
dbms_output.put_line('');
end printElements;
-- prints the attributes of each element in a document
procedure printElementAttributes(doc xmldom.DOMDocument) is
nl xmldom.DOMNodeList;
len1 number;
len2 number;
n xmldom.DOMNode;
e xmldom.DOMElement;
nnm xmldom.DOMNamedNodeMap;
attrname varchar2(100);
attrval varchar2(100);
begin
-- get all elements
nl := xmldom.getElementsByTagName(doc, '*');
len1 := xmldom.getLength(nl);
-- loop through elements
for j in 0..len1-1 loop
n := xmldom.item(nl, j);
e := xmldom.makeElement(n);
dbms_output.put_line(xmldom.getTagName(e) || ':');
-- get all attributes of element
nnm := xmldom.getAttributes(n);
if (xmldom.isNull(nnm) = FALSE) then
len2 := xmldom.getLength(nnm);
-- loop through attributes
for i in 0..len2-1 loop
n := xmldom.item(nnm, i);
attrname := xmldom.getNodeName(n);
attrval := xmldom.getNodeValue(n);
dbms_output.put(' ' || attrname || ' = ' || attrval);
end loop;
dbms_output.put_line('');
end if;
end loop;
end printElementAttributes;
begin
-- new parser
p := xmlparser.newParser;
-- set some characteristics
xmlparser.setValidationMode(p, FALSE);
xmlparser.setErrorLog(p, dir || '/' || errfile);
xmlparser.setBaseDir(p, dir);
-- parse input file
xmlparser.parse(p, dir || '/' || inpfile);
-- get document
doc := xmlparser.getDocument(p);
-- Print document elements
dbms_output.put('The elements are: ');
printElements(doc);
-- Print document element attributes
dbms_output.put_line('The attributes of each element are: ');
printElementAttributes(doc);
-- deal with exceptions
exception
when xmldom.INDEX_SIZE_ERR then
raise_application_error(-20120, 'Index Size error');
when xmldom.DOMSTRING_SIZE_ERR then
raise_application_error(-20120, 'String Size error');
when xmldom.HIERARCHY_REQUEST_ERR then
raise_application_error(-20120, 'Hierarchy request error');
when xmldom.WRONG_DOCUMENT_ERR then
raise_application_error(-20120, 'Wrong doc error');
when xmldom.INVALID_CHARACTER_ERR then
raise_application_error(-20120, 'Invalid Char error');
when xmldom.NO_DATA_ALLOWED_ERR then
raise_application_error(-20120, 'Nod data allowed error');
when xmldom.NO_MODIFICATION_ALLOWED_ERR then
raise_application_error(-20120, 'No mod allowed error');
when xmldom.NOT_FOUND_ERR then
raise_application_error(-20120, 'Not found error');
when xmldom.NOT_SUPPORTED_ERR then
raise_application_error(-20120, 'Not supported error');
when xmldom.INUSE_ATTRIBUTE_ERR then
raise_application_error(-20120, 'In use attr error');
end domsample;
show errors;

Struggling to have two document type attributes in the same notification

Hi All,
I need some help. I am working with Oracle Time and Labor, and am trying to get two document type attributes to play nice in the same notification message body.
One documentation type attribute is made available to me. Here is its attribute value:
JSP:/OA_HTML/OA.jsp?&OAFunc=HXC_TIMECARD&akRegionApplicationId=809&retainAM=Y&Action=ApprovalDetail&Timecard_id=-&APP_BB_ID-&ResourceId=-&RESOURCE_ID-&TimecardMode=TIMECARD-REVIEW&Review=Y&FromAppPage=YES&NtfId=-&#NID-&StartTime=-&FORMATTED_APP_START_DATE-
The second one I created as a PLSQL document. This one I have simplified to just a 'Hello World'.
When both are in the message body at the same time, the notification message body looks like this (the name of one of the document type attributes is 'TIMECARD'):
hello world Attribute TIMECARD refers to Framework Region JSP:/OA_HTML/OA.jsp?&OAFunc=HXC_TIMECARD&akRegionApplicationId=809&retainAM=Y&Action=ApprovalDetail&Timecard_id=-&APP_BB_ID-&ResourceId=-&RESOURCE_ID-&TimecardMode=TIMECARD-REVIEW&Review=Y&FromAppPage=YES&NtfId=-3614187-&StartTime=-&FORMATTED_APP_START_DATE-.
When either document type attribute exists by itself in the message, everything works as planned.
Any suggestions?

I think the problem here is caused when you token - substitute an attribute which appears in another attribute.
Suppose that you have two document type attributes as shown below:
1. CONTENT whose value is:
plsqlclob:PA_PWP_NOTIFICATION.SHOW_PWP_NOTIFY_PREVIEW/&CONTENT_ID
and
2. CONTENT_ID whose value is: 11629
Now, what happens is, while token substituting &CONTENT_ID in the first attribute, &CONTENT_ID is possibly being broken into
&CONTENT and replaced with a null value and then ID is left as is. The problem seems to be because CONTENTID is used
inside another attribute CONTENT.
The workaround here is to change the name of attribute CONTENT to some other name or change the attribute name CONTENT_ID
to something different.
In your case I suppose that the names of attributes you are having may be similar or one being subset of other. You can avoid the
problem by having different names (or name which is not part of another attribute's name).
If this does not solve the problem you can generate output of $FND_TOP/sql/wfmlrdbg.sql output for this notification id.
Hope that helps !!
Thanks,
Dilbagh

p tags with attributes not removed from JTextPane

We are using HTMLEditorKit with JtextPane to create a HTML Document Editor, for our project. [JDK 1.3.1.]
When we have a simple <p> tag for paragraph in HTML and we start deleting things from end of the document, it works fine. But when we have a <P> tag with attributes like <p align='CENTER'> the delete key deletes the characters but the cursor remains in the line below and doesnot move up as the characters of above para get deleted. The HTML also retains the <p align='CENTER'> tag, which should have been removed. It seems its not able to identify <p> tags with attributes as Html para tags, and so not deleting it.
How do we solve this without migrating to jdk1.4 ? Please help.

Usually attributes such as 'align=center' are deleted along with a tag, regardless of whether it is a p tag or another one. But you would have to carefully test what exactly gets deleted because attributes are not only stored with paragraphs. They can exist for single characters and as well come from a style sheet.
The best is to generate a dump of your document before and after deletion.
You can use something like the below code (it is not optimized at all and thus could be implemented better but it works) to produce a dump
public void listElements(Element elem, int indent) {
    int i;
    String is = getIndent(indent);
    String elemName = elem.getName();
    Document elemDoc = elem.getDocument();
    String cont = "";
    String theText = "";
    System.out.println(is + "--start-----");
    System.out.println(is + "Element Name:" + elemName);
    if(elemName.equals(new String("content"))) {
      try {
        theText = elemDoc.getText(
                elem.getStartOffset(),
                elem.getEndOffset() - elem.getStartOffset());
        System.out.println(is + "Content: " + theText);
        if(theText.indexOf("\r") > -1) {
          System.out.println(is + " plus \\r");
        if(theText.indexOf("\n") > -1) {
          System.out.println(is + " plus \\n");
      catch (Exception e) {
    listAttributes(elem, indent);
    if(!elem.isLeaf()) {
      for(i=0;i<elem.getElementCount();i++) {
        listElements(elem.getElement(i),indent+2);
    System.out.println(is + "---end----");
public void listAttributes(Element elem, int indent) {
    Object key;
    String attr;
    String attrName;
    int pos;
    String is = getIndent(indent);
    AttributeSet as = elem.getAttributes();
    Enumeration an = as.getAttributeNames();
    try {
      while(an.hasMoreElements()) {
        key = an.nextElement();
        attrName = key.toString();
        attr = as.getAttribute(key).toString();
        System.out.println(is + "Attribute Name: " +
                  attrName + " Attribute Content: " + attr);
        if(attr.indexOf("\r") > -1) {
          System.out.println(is + " plus \\r");
        if(attr.indexOf("\n") > -1) {
          System.out.println(is + " plus \\n");
    catch (Exception e) {
      e.printStackTrace();
}Hope that helps
Ulrich

BPEL 11g 1.1.6 -.7 XML document looses attribute names on enqueue

We are in the process of migrating BPEL processes from 10.1.2.3 to 11.1.1.6
We're using an AQ adapter to write inbound XML messages into an Oracle queue.
Our developer has ran into an odd situation -
When the message is written into the queue, the XML looses all the attribute names. The values are still there, but the names vanish...
Example...
<ShipNotice Version="3.0">
<Header>
<ThisDocumentIdentifier>
<DocumentIdentifier>12345</DocumentIdentifier>
</ThisDocumentIdentifier>
<ThisDocumentDateTime>
*<DateTime DateTimeQualifier="On">20130409T150425Z</DateTime>*
</ThisDocumentDateTime>
Becomes:
<ShipNotice Version="3.0">
<Header>
<ThisDocumentIdentifier>
<DocumentIdentifier>12345</DocumentIdentifier>
</ThisDocumentIdentifier>
<ThisDocumentDateTime>
*<DateTime ="On">20130409T150425Z</DateTime>*
</ThisDocumentDateTime>
(Note the DateTimeQualifier attribute is gone.)
This happens for every attribute in the document with the exception of the root element...
Does this ring any bells with anyone?

Correction on that... the attribute in the root element is also removed.. my bad...
So I should have said...
Example...
*<ShipNotice Version="3.0">*
<Header>
<ThisDocumentIdentifier>
<DocumentIdentifier>12345</DocumentIdentifier>
</ThisDocumentIdentifier>
<ThisDocumentDateTime>
*<DateTime DateTimeQualifier="On">20130409T150425Z</DateTime>*
</ThisDocumentDateTime>
Becomes:
*<ShipNotice ="3.0">*
<Header>
<ThisDocumentIdentifier>
<DocumentIdentifier>12345</DocumentIdentifier>
</ThisDocumentIdentifier>
<ThisDocumentDateTime>
*<DateTime ="On">20130409T150425Z</DateTime>*
</ThisDocumentDateTime>
...

Generating XML with attributes using XSU

Oracle document claims if the sql is:
select empno as @empno from employee
Using XSU to generate XML will produce and XML document with EMPNO as an attribute instead of element name. But this does not seem to work. There is an exception:
<ERROR>oracle.xml.sql.OracleXMLSQLException: Character '&' is not allowed in an XML tag name.</ERROR
Is there anything wrong or is there a work around

Oracle document claims if the sql is:
select empno as @empno from employee
Using XSU to generate XML will produce and XML document with EMPNO as an attribute instead of element name. But this does not seem to work. There is an exception:
<ERROR>oracle.xml.sql.OracleXMLSQLException: Character '&' is not allowed in an XML tag name.</ERROR
Is there anything wrong or is there a work around

Creation of Material Documents With Mvt Type

On Performing Post Goods Issue (PGI) in one Plant in case of Plant to Plant Dispatches, there should be Inbound delivery created for already created Purchase Order (PO). In addition after creation of inbound delivery, there should be material document created with 103 movement. This Material document is triggered when the inbound delivery is saved. Once Warehouse processes are finished, then Post Goods Receipt (PGR) happens, so 101 Movement Type happens for Purchase Order. PGR document should trigger one more material document with 104 movements; this document is reversal for material document with 103 movement type.
can any one suggest to enhance SAP for this?
Moderator message : Requirements dumping is not allowed, show the work you have already done. Thread locked.
Edited by: Vinod Kumar on Oct 21, 2011 5:18 PM

Hi Nitin,
Before creating the Service type of product, you have to define the Base category for Service type product. Generally the category for service will be created under the R3 hierarchy R3PRODSTYPE. You can create this category using the TCode:
COMM_HIERARCHY. Here you have to select the product type as Service and have to assign the set types to the category.
You can create a service product using the transaction : COMMPR01 -> Click on Service ICON -> Select the Category for Service Type. Then fill in the details for Service Product description, Service ID(Based on number range settings for products), Language.
Also fill other details like Base Unit of measure, Pricing condition for different sales areas for the service product.
Since you are using CRM7.0, you can do all these activities using a POWER USER role.
For more information about Set types and hierarchies please refer the following help link:
http://help.sap.com/saphelp_crm70/helpdata/EN/46/57672501a208e7e10000000a114a6b/frameset.htm
Hope this helps!
Regards,
Chethan

Printig documents with attributes

Similar Messages

Maybe you are looking for