Solution : https://service.sap.com/sap/support/notes/551451 (SAP Service marketplace login required)
Summary :
SAP Note addresses the issue of Business Document Service (BDS) document transport which fails while using the Business Document Navigator (BDN), displaying error messages SBDS 330, in 331, in 332. The root cause lies in the report category’s BDS and the linked attachment content model, which determine the document’s transportability via linked database tables. Transportability also hinges on the document classes’ characteristics such as client dependency and delivery class. Four main BDS standard models each have varying transportability attributes. Solution involves using transaction sbdsv1 wisely to redefine associations without impacting existing documents and ensuring selected content models accommodate transport requirements.
Key words :
bds_loc1/bds_poc1/bds_rec1/bds_conn00 client =, =nobds_loc2/bds_poc2/bds_rec2/bds_conn05 client =, =yesbds_loc6/bds_poc6/bds_rec6/bds_conn06 client =, =yesbds_loc7/bds_poc7/bds_rec7/bds_conn04 client =, terms error messages sbds 330, assigned business documents exist, previously unassigned application classes, content model indirectly determines, observe client dependency, ad hoc assignment
Related Notes :
| 782614 | Using external Content Server in the BDS |