Problem in Transaction code OAER
Problem in Transaction code OAER
by ravs4u » Tue Sep 13, 2005 4:42 am
Hi ,
I uploaded one Excel Sheet using transaction OAER.
Class Name ZXL, Class Type OT and Object Key as Export.
While trying to assign it to a transport request, i clicked the icon for transport. But it is showing the error..
Message No: SBDS330
"The Customizing settings for the document do not allow a transport"
Please let me know how can I assign it to the transport request.
Regards,
Ravi
by Snowy » Tue Sep 13, 2005 5:15 am
check SE06 and SCC4
by vnenov » Wed Sep 14, 2005 7:20 am
The transportability of documents depends on the Business Document Service(BDS) of the report category.
The class of the application object is assigned to a content model. The content model indirectly determines the database tables used via the document classes used and thereby also determines transportability. In addition to content models that are used proprietarily by an application, there are 4 standard BDS models that share applications with a low dataset. These standard models are characterized as follows by document classes, link table, client dependency, delivery class and transportability :
BDS_LOC1/BDS_POC1/BDS_REC1/BDS_CONN00 Client =yes, Del.='A' Trans.=no
BDS_LOC2/BDS_POC2/BDS_REC2/BDS_CONN05 Client =no, Del.='E' Trans.=yes
BDS_LOC6/BDS_POC6/BDS_REC6/BDS_CONN06 Client =yes, Del.='C' Trans.=yes
BDS_LOC7/BDS_POC7/BDS_REC7/BDS_CONN04 Client =yes, Del.='E' Trans.=yes
The context of report categories and document classes is displayed via transaction sbdsv1. An ad hoc assignment to the BDS_LOC1/... content model is formed by creating business documents for previously unassigned application classes. These business documents then become transportable.
Assignments can also be maintained in transaction sbdsv1. However, no entries for object classes for which documents already exist must be changed using this transaction. The documents would no longer be accessible afterwards.
However, if you ensure that no assigned business documents exist for a report category yet, or if a new entry is created, you can influence transportability by choosing a suitable standard model. In this case, you must observe client dependency, delivery class, and data volumes where necessary.
Vnenov
The class of the application object is assigned to a content model. The content model indirectly determines the database tables used via the document classes used and thereby also determines transportability. In addition to content models that are used proprietarily by an application, there are 4 standard BDS models that share applications with a low dataset. These standard models are characterized as follows by document classes, link table, client dependency, delivery class and transportability :
BDS_LOC1/BDS_POC1/BDS_REC1/BDS_CONN00 Client =yes, Del.='A' Trans.=no
BDS_LOC2/BDS_POC2/BDS_REC2/BDS_CONN05 Client =no, Del.='E' Trans.=yes
BDS_LOC6/BDS_POC6/BDS_REC6/BDS_CONN06 Client =yes, Del.='C' Trans.=yes
BDS_LOC7/BDS_POC7/BDS_REC7/BDS_CONN04 Client =yes, Del.='E' Trans.=yes
The context of report categories and document classes is displayed via transaction sbdsv1. An ad hoc assignment to the BDS_LOC1/... content model is formed by creating business documents for previously unassigned application classes. These business documents then become transportable.
Assignments can also be maintained in transaction sbdsv1. However, no entries for object classes for which documents already exist must be changed using this transaction. The documents would no longer be accessible afterwards.
However, if you ensure that no assigned business documents exist for a report category yet, or if a new entry is created, you can influence transportability by choosing a suitable standard model. In this case, you must observe client dependency, delivery class, and data volumes where necessary.
Vnenov
- vnenov
Form：http://www.sapfans.com/forums/viewtopic.php?f=12&t=203391
浙公网安备 33010602011771号