Dear Partners,
join us for the next edition of our quarterly update call for SAP Partners in the area of PLM, PPM and Product Safety and Stewardship on
28th October, 4:30 CET
Agenda
- Update on Solution Launches for
- Product Costing
- SAP Cloud for Product Stewardship
- SAP Innovation Management
- Demo Landscape for Partners
Best Regards, Andrea
Increasing profit with tailor-made products?
The needs of the modern digital economy places unprecedented demands on discrete manufacturers to bring innovation faster to the market.
Product individualization is a major trend across the most industries. Empowered customers can configure their individual dream car, order personalized sports shoes, add personal messages to their Nutella jars and much more. In the B2B segment, tailor-made products and services are transforming the market as well.
But delivering individualized, smart connected products at a rapid time throws up its own challenges for manufacturers. How can you reduce R&D and manufacturing costs while increasing your number of product variants? How can you ensure that your entire product portfolio complies with global regulations? How can you manage all that product data for increasingly complex products?
Join SAP´s free webinar on November 4th to understand how the latest innovations in SAP PLM helps to address these challenges. Learn how SAP PLM helps to manage and deliver customer-driven engineering innovations into the market by orchestrating all business functions and bills of material requirements.
DATE: Wednesday, November 4, 2015
Time: 11 am EDT / 08:00am PDT / 5:00pm CET
Registration link: click here
By the way, there are more free on-demand webcasts available on our virtual event platform for SAP Extended Supply Chain.
Hope to see you online on November 4.
Join our Webcast on November 18 to learn how the SAP Product Lifecycle Management application can help you develop compliant, sustainable products
Constant changes in regulatory and reporting demands have always been a challenge for product development in the process industries.
Today, these challenges are growing, as consumers expect a greater variety of product offerings and demand more information about these formulated products.
Being able to develop and deliver innovative products that meet these increased demands in an efficient way while maintaining quality is imperative.
Software tools to support this innovation process are becoming more and more important.
Attend this Webinar to understand how the latest innovations in SAP Product Lifecycle Management help process manufacturers to manage and deliver customer-driven innovations in an intelligent and efficient manner.
Don’t miss this unique opportunity to:
Register now to join this informative session. We look forward to seeing you there!
The following functional and usability enhancements for engineering records are included in this innovation,
This feature enables you to specify the customer-specific handling of tasks related to engineering records when decisions are made for these tasks.
For rejection decisions in Engineering Record, SAP delivers a default class which causes the system to cancel parallel tasks, skip sequential tasks, and, depending on other Customizing settings, switch the status, or load a new process route template. As you see the screen below.
Find the feature detail introduction document here
Find the technical How-To-Guide here
Find the demo video here
This feature enables you to do the following:
These e-mails contain the task details, as well as a direct link to the task. You can use the e-mail templates provided by SAP or create your own. As you see the screen below.
When the task status is changed, the e-mail based on the template is sent. The recipients of the mails are defined based on the people involved in the process route task. The recipients, subject, and further attributes of the e-mail can be changed, if required.
Find the feature detail introduction document here
This feature enables you to view and analyze changes, that is, insertions, deletions, or updates, that have been made to an engineering record by choosing Additional Functions –> Display Change Documents.
Change documents are available for changes made to the following change document objects:
The changes are displayed in a table, and you can quickly and easily see, for example, the user who made a change or the type of change as you can see in the screen below.
Find the feature detail introduction document here
Find this innovation here on the Innovation discovery
The following functional and usability enhancements for Global Process Route Templates are included in this innovation,
This feature enables you to use process routes based on global process route templates in all GOS object types on the PLM Web UI. You specify the object type when you create the global process route template. Once you activate the global process route template, the resulting process route is available for that object type. The following object types are now available:
The default object type if not other object type is specified is the Engineering Record when creating a Global Process Route Template as it shows in the screen below,
Find the detail feature introduction here
This feature enables you to set up engineering record types for the object type PLM_ECR (engineering records) for use in global process route templates and when loading and inserting process routes in your engineering records in the PLM Web user interface.
You can assign a record type to a global process route template when creating as you see the screen below,
If you assign a record type to a global process route template, then this global process route template can only be used for this type of engineering record and the record type cannot be subsequently be changed.
If you do not use this feature, you cannot add record types to global process route templates and your global process route templates are valid for all engineering records.
Find the detail feature introduction here
Find this innovation here on the Innovation discovery.
The following functional and usability enhancements for process routes are included in this innovation,
This feature enables you, as a processor or change coordinator, to forward process route tasks in your engineering records to other system users. As you see the screen below.
Find the detail feature introduction here
This feature improves the usability of the process route log in the PLM Web UI with the following changes:
As you see the screen below.
Find the detail feature introduction here
This feature enables you to have greater transparency on exactly which user processed a task in a process route, by providing links to the processors in the Process Tasks column. The link opens the User Details popup window if there is an individual processor, or the Available Processors popup window if there is a user group, job, or position. As you see the screen below.
Find the detail feature introduction here
Find this innovation here on the Innovation discovery.
This innovation enables you to significantly speed up your processing of engineering record data. To achieve this, you migrate change items in engineering records from the case management-based XML storage to the engineering record database tables.
Find the How-To-Guide ‘Engineering Record Change Item Migration’ here
Find the How-To-Guide ‘Extension of Change Items’ here
Find this innovation here on the Innovation discovery.
Hello SAP Community,
No matter whether you plan to integrate CATIA V6 (CATIA 3DEXPERIENCE) with SAP, mesh a full Feature 3DEXPERIENCE solution with SAP across a series of product developement phases, or manage SAP material masters via ENOVIA - our Integration will match your Business process.
The CENIT SAP integration for 3DEXPERIENCE is the most flexible solution.
Synchronous and asynchronous process driven system Integration with bi-directional inerchange of IP.
Visit us at our live Workshop in Stuttgart, March 16, or join the webinar online.
Core functions of the 3DEXPERIENCE-SAP integration
For more Information visit our Website: www.cenit.com
Best,
Alexander
CENIT
SAP Solutions
INTRODUCTION:
Attachment service is a re-usable UI component in S/4HANA application. Applications can make use of this component to deal with attachment related functionality. Uploading, downloading, renaming, and deleting an attachment from or to the parent application are some of the basic features supported by Attachment Services. This re-usable component is based on UploadCollection control from UI5 foundation.
Attachments are linked to business objects based on SAP Document Management System (DMS) or Generic Object Services (GOS).
The attachment content is stored on the HCP (HANA Cloud Platform) Document Service (in cloud scenario) using SAP KPRO (Knowledge Provider) and it is stored on the configured content server (in on-premise scenario).
ATTACHMENT SERVICES UI:
CUSTOMIZING:
You can customize attachment services by going to the path: SPRO-> Cross Application Components-> Document Management-> Additional Settings - Simplification
CONSUMPTION STRATEGY:
HOW TO CONSUME ATTACHMENT SERVICE BASED ON DMS:
As a pre-requisite, a document type, an object type, and their linkage has to be configured in the system.
In this case, where we are consuming attachment services based on DMS, a Document Info Record (DIR) is created in the background. The DIR is completely abstracted from the end user. It is not required for the end user to have knowledge on DIR and its functionality to deal with attachments in different applications. This makes the process simpler by treating the attachments as attachments in various applications instead of complicating with a technical business object behind the scenes.
What is happening behind the scenes when a user adds an attachment?
The attachments are added with respect to a parent object. They cannot be made independent, a context is always required. Attachment is added corresponding to an object type and a key. This object type is the parent business object. A DIR is created in the backend and linked to this object type. On saving, the attachments added for an object type gets linked to the DIR which was created. This DIR creation process and linkage of attachments with that DIR is completely hidden from the end user. In SAP GUI, if we open the same DIR, we can see the attachments and also the object link.
Example: For material master object (object type: MARA), attachments are added in the UI. If we open the same material in SAP GUI (backend), we can see a DIR created with the same attachments that were added from the UI. (Assuming MARA is DMS scenario). The advantage is instead of creating the DIR and adding attachments to it and then creating an object link, the user will now only add attachments to the desired object type. Attachment services will create a DIR in the backend and link attachments to it.
GUI SCREEN FOR DMS SCENARIO :
Another example which explains GOS scenario is Purchase Order (Object Type: EKKO). Here, the attachments added from UI can be seen under the attachments list if we open the same material in SAPGUI.
NOTE:
Consumers can see from SAPGUI, only if there is an object link to the consuming object and consuming object has a SAP GUI screen.
.
Also, attachment services comes up with a BAdI which supports a consuming application to choose document type. They may require different document types to be mapped to a single object type. Normally, if there are more than one document type configured, the first one will be picked by default. But with this BAdI extension, the consuming application will have the flexibility to choose the document type from the customizing entries.
It is recommendation for cloud consumption to have one document type mapped to one object type. But in case of on-premise consumers there is a n:1 mapping and consumers have the flexibility to determine the document type at runtime.
HOW TO CONSUME ATTACHMENT SERVICES BASED ON GOS :
Earlier in SAP ERP applications, attachments were dealt via GOS (Generic object services). In order to support the previous applications to create or read attachments from FIORI UI to SAP GUI and vice-versa, this support is available.
Consuming applications can pass their technical object type and object key and add attachments. User can go to that object type in SAP GUI and can see the added attachments if they have a SAP GUI screen.
Rename of attachments is not possible in case of GOS attachments as it is not supported by GOS.
GUI SCREEN FOR GOS SCENARIO (Material Master Object)
Attachment service supports a new concept called ‘Key Replacement’. If the attachments are added to any object which is not permanent or just created and not saved, in that case attachments will be added to the temporary key and during save when the object is permanently saved, this temporary key is replaced by the permanent key.
KEY POINTS:
Attachment Service provides consumers to add their own business functionality to the existing functionality.
The following BAdI extensions can be efficiently consumed to achieve multiple functionalities:
1) BAdI: BADI_CV_ODATA_ATTACH_DRAFT_HDL:
Method: DRAFT_DELETE_AVOID
As already explained about the ‘Draft’ scenario in Attachment Service, where the attachments are in draft state until an explicit save is done. With this scenario, a situation can occur where there are multiple draft attachments which have not been saved since long time. As we know that ‘OnCloud, Space is equal to Money’, so these attachments should be deleted as they are unnecessarily consuming space. Deletion of draft attachments is an optional administrative activity. Hence, a report program is available for administrators to delete all the draft attachments which have been introduced with an intention to efficiently utilize the cloud space. This means that long pending draft attachments which are not saved can be deleted so that the space occupied by those attachments is removed. This BAdI will be called from the report DELETE_DRAFT_ATTACHMENTS, which is used by Admin to delete the draft contents. In order to avoid an attachment getting deleted, the parent application can write an implementation to avoid deletion.
2) BAdI: BADI_CV_ODATA_ATTACH_DRAFT_HDL
Method: DETERMINE_DOCUMENT_TYPE
Sometimes it is possible that a consuming application needs more than one document type to be mapped to an object type. Currently, there is a Customizing available for mapping the document type to an object type in DC10. In this Customizing, it is possible to maintain the mapping of one object to different document types. But if there are more than one document types configured, the first one will be picked. Now with this BAdI solution, the consuming application will have the flexibility to choose the document type from the customizing entries. This BAdI has an importing parameter which receives the table containing the list of object types and document types from table TDWO as per the customizing in DC10. This table contains entries of all document types allowed for an object type and hence passed to change to valid document type. The BAdI implementation can set a document type to the appropriate object type if only it is available in the DC10 customizing. If any other document type is set, the save process will fail. After receiving the table of entries, the users can determine which document type they want to pick for the corresponding object type. The changing parameter is of row type of Draft table for attachments, that is the complete information of attachments is received and can be changed. The consuming application can create an implementation which can depend upon various attributes like mimetype, WSapplication type, filesize, and so on to determine the document type. Only DOCUMENTTYPE field is compared and change is accepted.
NOTE: Recommendation for cloud consumption is to have one document type mapped to one object type (1:1 mapping). But in case of on-premise consumers there is a n:1 mapping and consumers have the flexibility to determine the document type at runtime.
3) BAdI: BADI_CV_ODATA_ATTACHMENTS_AUTH
Method: CHECK_AUTHORIZATION
This BAdI method is capable of supporting multiple features:
a) Assume a situation where you want the users to have authority to only read all the attachments but not to rename or delete them. How can you restrict them?
This BAdI provides solution to this problem.
Previously before this solution, providing object type and object key would suffice to load attachments corresponding to that object key. With this newly introduced BAdI method, first the authorization check is done against the operation being performed on attachments i.e READ (display list of attachments), CREATE (adding attachment), and DELETE (delete Attachment). This is a filter-based BAdI having filters for OBJECT_TYPE and OBJECT_TYPE_LONG. So there can be multiple active implementations and it will be specific for each object type. If Implementation exists for an object type, only then users will be able to perform any action on attachments related to that object type and key. Also, in the implementation based on activity type, it is possible to restrict or allow any activity.
b) This BAdI method is also capable enough to restrict uploading of attachment or getting list of attachment based on check on any of the attachment properties. It can restrict based on mimetype, file extension of attachment, created by, created at date of the attachment, or even file size of the attachment. If you have any condition that file size greater than 10 MB should not be displayed or attachments will extension .txt should not be loaded or any similar scenario, this BAdI method addresses such requirements. A changing parameter having list of all attachments is passed to the BAdI. In the implementation, based on mimetype or file extension of the attachments, users can restrict CREATE and READ operation.
4) BAdI : BADI_CV_ODATA_ATTACHMENTS_AUTH
Method : CHECK_USER_AUTHORIZATION
For the same scenario as mentioned above, where you want users to only to be able to read the attachments and not perform any action on them. Then using this BAdI you can control the visibility of rename, delete, and add action available for attachments. So now if a particular user is unauthorized to perform any particular action, then the user won’t see the corresponding button on the UI.
Before restricting delete and rename actions based on User , UI appears as :
After restricting delete and rename actions , UI appears as :
This blog intends to raise awareness about consequences to custom functionality when upgrading from SAP PLM 7.02 (EHP6) to SAP PLM 7.4.7 (EHP7). In addition to explaining the consequences, a solution is given to minimize the impact caused by the upgrade.
I doubt no SAP customers are live with a out-of-the-box standard SAP PLM solution. Most SAP customers have the need to customize, enhance, modify, etc. the standard solution. If you are one of those SAP customers or an implementation partner for one, read on.
Upgrading from EHP6 to EHP7 changes core APIs used by the PLM Web UI. The most disruptive changes are contained in SAP notes 1861056 and 1980389. The SAP notes change the implementation of methods GET_HEADER and CHANGE_HEADER of the class /PLMI/CL_DIR_BO. The class /PLMI/CL_DIR_BO, as you may already know, is a central class in PLM Web UI. The class serves as a layer between PLM Web UI and SAP DMS. The disruptive change is that the methods GET_HEADER and CHANGE_HEADER no longer work correctly if used outside of the PLM Web UI context, be it from SAP GUI, RFC or background job.
The disruptive code in method GET_HEADER
case /PLMU/CL_FRW_APPL_CNTRL=>GV_MODE.
WHEN'C'.
lv_activity = '02'.
WHEN'D'.
lv_activity = '03'.
WHEN'I'. " SAP Note 1962595
lv_activity = '01'. " SAP Note 1962595
ENDCASE.
Similarly, the disruptive code in method CHANGE_HEADER
IF( /plmu/cl_frw_appl_cntrl=>gv_mode = /plmu/if_frw_constants=>gc_mode-change )AND( /plmi/cl_dir_bo=>MV_NOT_SAVED isINITIAL).
lv_tcode = 'CV02'.
The problem is that the static attribute /PLMU/CL_FRW_APPL_CNTRL=>GV_MODE has a value of ' ' outside the PLM Web UI context, any code depending on the correct mode of operation (Display, Change or Insert) will work incorrectly.
Solution by SAP
I reported the problem to SAP support and it was escalated properly. The official answer from SAP is that the PLM APIs are not released for customer use and customers are responsible for making required changes to their own code. Based on the answer I was provided, SAP doesn't even consider the issue severe enough to warrant a SAP KBA.
If you have implemented any custom functionality, enhanced or modified existing functionality that uses the /PLMI/CL_DIR_BO class, chances are your changes won't work after the EHP7 upgrade (or whenever the SAP notes mentioned previously are installed in the system).
Regardless whether you are planning an upgrade or not, you should make sure that your custom functionality isn't using the GET_HEADER or CHANGE_HEADER methods of class /PLMI/CL_DIR_BO, assuming the custom functionality is used from SAP GUI, RFC or background jobs. You should start changing your code to use DMS function modules instead of using the PLM Web UI APIs.
I wonder how long SAP is going to stick to their "not released for customer use hence we can break it whenever we want even if customers suffer" mantra. It might have worked in the in the 90's but somehow I don't believe it will work in the future. Now that all efforts are on HANA, let's hope they do a better job with APIs there.
INTRODUCTION:
In this blog I'm going to explain how to consume the Attachment Service reusable UI component in Smart Template applications.
Attachment service is a re-usable UI component used in S/4 HANA on-premise and cloud applications. Applications can make use of this component to deal with attachment related functionality. Uploading, downloading, renaming, and deleting an attachment from or to the parent application are some of the basic features supported by Attachment Services. This re-usable component is based on UploadCollection control from UI5 foundation.
The purpose of smart template in S/4 HANA is to reduce the amount of front-end code required for building applications and centrally provide a high code quality through predefined templates and controllers.
Attachment service UI component can be consumed easily in the smart template by adding the view and controller using the extension and creating the facet where we can add attachment component.
Attachments are linked to business objects based on SAP Document Management System (DMS) or Generic Object Services (GOS). The attachment content is stored on the HCP (HANA Cloud Platform) Document Service (in cloud scenario) using SAP KPRO (Knowledge Provider) and it is stored on the configured content server (in on-premise scenario).
Prerequisite:
Steps to create the smart template application.
System Requirements
SAP Web IDE 1.17 (or higher) including the annotation modeler plugin (for more information see the Annotation Modeler in the documentation of SAP Web IDE)
SAP NetWeaver 7.5 SP01 or higher.
Note
We recommend that you download the most up-to-date version to ensure that you have the latest features.
The below example will explain how to create smart template application using an existing gateway service (ZSMART_ATTACH_100).
1. Select the Workspace -> New -> Project from Template.
2. Chose the Smart Template Application and click on Next
3. Enter Smart Template Application details as per the requirement.
Project name: It is unique and descriptive.
Namespace: Is mandatory attribute which is unique identifier of the app, which must correspond to the component ID.
Enter the Application Component Hierarchy and Fiori ID and click on next
Application Component Hierarchy: The application component hierarchy is based on the project component.
Fiori ID: The Fiori ID is entered based on the creation of your project in the project portal.
4. Enter the System and Gateway service and click on next
Select the Service catalog and chose the UI front end system where Gateway service is available.
5. Check the annotation model is available for application if it is available leave it.
You can add the separate annotation files by clicking on the +Add Annotation Files
Click on Next
6. Select the OData Collection and OData Navigation from the drop down list and click on next and Finish.
Based on the Gateway service select the collection and the Navigation from the drop down list.
After creating the smart template application the below files are generated in the application.
The below files need to be modify to add attachment reuse component library in the application are.
1. Neo-app.json:
The neo-app.json file contains all project settings for SAP Web IDE and is created in the root folder of your project. It is a JSON format file consisting of multiple configuration keys. The most important setting for you to configure is the path where the SAPUI5 runtime is located when starting the app.
2. Manifest.json :
The application descriptor provides a central, machine-readable and easy-to-access location for storing metadata associated with an application or application component.
The data is stored in json format in the manifest.json file. The developer creates the file with attributes in different namespaces. It contains, for example, the app ID, the version, the data sources used, along with the required components and libraries. The existence of the manifest.json file must be declared in the component metadata, which is then delivered as part of the application archive. After delivery, the file is read-only.
3. Component.js:
The component.js file is the component controller and provides the runtime metadata and the component methods.
The metadata provide the information to ensure the completeness of the elements of which the component consists of. This facilitates the decoupling of the application logic as much as possible from the logic within a particular component.
How to consume attachment service component in smart template applications and run via Fiori Launchpad Tile.
1.In smart template application click on the neo-app.json file.
Add the library code and the header white list parameter code as given below.
{
"path": "/webapp/resources/sap/se/mi/plm/lib/attachmentservice",
"target": {
"type": "application",
"name": "semiplmlibattachmentservice",
"preferLocal": true
},
"description": "Reuse Library for Attachment Control Component (River RDE)"
},
{
"path": "/resources/sap/se/mi/plm/lib/attachmentservice",
"target": {
"type": "application",
"name": "semiplmlibattachmentservice",
"preferLocal": true
},
"description": "Reuse Library for Attachment Control Component (River RDE)"
},
{
"path": "/src/main/webapp/resources",
"target": {
"type": "application",
"name": "semiplmlibattachmentservice",
"preferLocal": true
},
"description": "Reuse Library for Attachment Control Component (River RDE)"
},
Add the Header whitelist parameters given below.
"headerWhiteList": [
"objecttype",
"objectkey",
"MarkForDeletion",
"documentType",
"documentNumber",
"documentVersion",
"documentPart",
"semanticobjecttype"
]
2. In smart template application click on the manifest.json file.
Add the attachment library code in the dependencies section.
"sap.se.mi.plm.lib.attachmentservice": {}
Add the attachment component code in the components section
"sap.se.mi.plm.lib.attachmentservice.attachment": {}
. 
3. In smart template application click on the component.js file.
Add the below code to as shown.
dependencies: {
libs: ["sap.m", "sap.se.mi.plm.lib.attachmentservice"],
components: ["sap.se.mi.plm.lib.attachmentservice.attachment"]
}
4. To create the view and controller as shown below.
Right Click on the application select New->Extension
Select object page and click on next
Select the page from the drop down list and Facet which one you want to use.
Select the Radio button as per your requirement.
Select the View as a new facet details
In this example Originals Facet is chosen so the new ATTACHMENTS facet is visible after ORIGINALS facet
Scroll down the page and give view name and facet name click on next and finish.
Now you will see the view and controllers in the ext folder as shown below.
5. Now add the view detail code given below in the view.xml page.
<core:ComponentContainer id="AttachmentsComponentContainer" propagateModel="true"/>
6. Add the controller code given below in the controller.js file
onInit: function() {
// sKey and sObjectType have to be set according to the business object
// Here in example, I’m using purchase order as object
var sKey = "ActivePurchaseOrder";
var sDraftKey = "PurchaseOrderDraftUUID";
var sObjectType = "EKKO"; // EKKO stands for Purchase Order
var oAttachComp = this;
var sMode = "{= ${ui>/editable} ? 'C' : 'D' }";
this.getOwnerComponent().getModel().attachRequestCompleted(function() {
var sCurrentKey = oAttachComp.getView().getBindingContext().getProperty(sKey);
if (!sCurrentKey) {
sCurrentKey = oAttachComp.getView().getBindingContext().getProperty(sDraftKey);
}
if (!oAttachComp._oAttachmentComponent || sCurrentKey !== oAttachComp.sDisplayedKey) {
oAttachComp.sDisplayedKey = sCurrentKey;
if (oAttachComp._oAttachmentComponent) {
// If the component already exists refresh it
oAttachComp._oAttachmentComponent.refresh(sMode,sObjectType, oAttachComp.sDisplayedKey);
} else {
// Create component and assign it to the component container
oAttachComp._oAttachmentComponent = sap.ui.getCore().createComponent({
name: "sap.se.mi.plm.lib.attachmentservice.attachment",
id: oAttachComp.createId("AttachmentsComponent"),
settings: {
mode: sMode,
objectKey: oAttachComp.sDisplayedKey,
objectType: sObjectType
}
});
oAttachComp.byId("AttachmentsComponentContainer").setComponent(oAttachComp._oAttachmentComponent);
}
}
});
}
Now change the controller logic according to business object type is passed to sObjectType
And object key is passed to sKey.
7. Finally the attachment component is integrated to the smart template application and looks like this in application.
After adding the attachment component to your application the “ATTACHMENTS” facets is visible in the object page after all your facets.
Here in this example ATTACHMENTS facet is visible after the “ORIGINALS” because in this example in step 4 it is mentioned after Originals facet it is displayed after this.
General Information and Object links are used in the current example it will be displayed in this example only, these will not be displayed in your application
Experts agree: We are in the middle of an industrial revolution. The future market will be driven by connected products, technologies and processes. Mark your calendar and experience how you can prepare your company and capitalize the opportunities ahead.
Hear about new solutions, trends and innovations for R&D / Engineering at the SAP PLM Infodays:
You are invited to join us at the SAP PLM Infodays, 27th and 28th of June in Walldorf
Mark your calendar today. More details will be announced soon at this page, at sap.com and via an invitation mail. Please do not hesitate to contact us directly at plminfoday@sap.com if you got questions upfront.
We are looking forward to welcoming you and your colleagues in Walldorf.
Arend Weil
Service Offering Manager
Today we were blocked from recreating indices for PLM search because of one broken ER in the system, the indexing short dumped while trying to close an ER with inconsistent sub-components. I tried all the standard methods, even tried to use /PLMI/CL_ECR_BO->DELETE_CHANGE_RECORDS without success. I then found out about BAPI_CASE_DELETE but even that wouldn't work because of the inconsistency with the ER in question. However, I ended up using BAPI_CASE_DELETE because that was the easiest to cheat around.
Disclaimer: do not attempt the following unless you know what you are doing. Even if you do, I do not take any responsibility if you happen to break your system by following these instructions. You have been warned!!!
Navigate from BAPI_CASE_DELETE to CL_SCMG_CASE_API->IF_SCMG_CASE_API~DELETE and then to CL_SCMG_CASE->IF_SCMG_CASE~DELETE. Locate the code which is checking each sub-component for authorization and place a break point following the call.
TRY.
READTABLE gt_subcomp_fcodes INTO wa_fcode WITHKEY fcode = <wa_subcomponent>-fcode.
IF sy-subrc = 0.
IF wa_fcode-classname ISNOTINITIAL.
ls_subcom_clas_method-clsname = wa_fcode-classname.
ls_subcom_clas_method-cpdname = 'CHECK_ACTIVITY_AUTHORIZATION'.
CALLFUNCTION'SEO_METHOD_GET_DETAIL'
EXPORTING
cpdkey = ls_subcom_clas_method
EXCEPTIONS
not_existing = 1
no_method = 2
OTHERS = 3.
IF sy-subrc <>0.
lb_activity_is_authorized = if_srm=>true.
* method CHECK_ACTIVITY_AUTHORIZATION does not exist..default auth to be true
*this may occur for subcomponents created by other appl & customer
CONTINUE.
ELSE.
TRY.
CREATEDATA lcl_subcomp_ref_var TYPEREFTO(wa_fcode-classname).
ASSIGN lcl_subcomp_ref_var->* TO<wa_subcomp_clas_instance>.
<wa_subcomp_clas_instance> ?= <wa_subcomponent>-class.
ls_string = 'CHECK_ACTIVITY_AUTHORIZATION'.
lcl_subcomp_obj ?= <wa_subcomp_clas_instance>.
CALLMETHOD lcl_subcomp_obj->(ls_string)
EXPORTING
im_activity = if_srm_document=>act_delete
im_skip_authorization = if_srm=>false
IMPORTING
ex_activity_is_authorized = lb_activity_is_authorized.
*--keep check as TRUE if the check_activity_authorization is not implemented by
*--component or the class is different.
CATCH cx_root.
lb_activity_is_authorized = if_srm=>true.
lb_activity_is_authorized = if_srm=>true.
ENDTRY.
ENDIF. " close of IF sy-subrc <> 0.
IF lb_activity_is_authorized = if_srm=>false. " <-- place break point here
MESSAGE s009(scmg_case)DISPLAYLIKE'E'.
RAISE EXCEPTION TYPE cx_srm_sp_client.
ENDIF.
ENDIF. " close of IF wa_fcode-classname IS NOT INITIAL
ENDIF. " close of IF sy-subrc = 0
CATCH cx_scmg .
RAISE EXCEPTION TYPE cx_srm_sp_client.
ENDTRY.
Whenever the execution reaches your break point, change the value of lb_activity_is_authorized to 'X'. At the end of the execution your inconsistent ER will be deleted and you will be able to create indices for PLM search.
While not pretty, the solution works. In my opinion there should be a standard report to either repair ERs or delete them if they are beyond repair.
1. DOCUMENT MANAGEMENT SYSTEM
1.1 PURPOSE
SAP Document Management meets all these complex requirements. In addition to managing documents, it also coordinates document processing. You can automate the entire life cycle of a document: from document creation to document storage, from access to update. Each document can be accessed immediately from any computer in the network.
1.2 AUTHORIZATION OBJECTS RELATED TO SAP DMS
1. C_DRAW_TCD (Activities for Documents) - This object controls which users can processwhich document info records, based on a combination of activity and document type.
2. C_DRAW_TCS (Status-Dependent Authorization) - This object controls which users canprocess which document info records, based on a combination of activity, document type, and status.
3. C_DRAW_STA - This object controls which statuses can be set for which document type.
4. C_DRAW_BGR (Authorization Group) - This authorization object allows you to limitaccess to individual documents.
5. C_DRAW_DOK (Document Access) - This authorization object controls for which originaldata of a specific document type there are access authorizations.
6. C_DRAD_OBJ (Object Link) - This object controls which users can process whichdocument info records, based on a combination of activity, object, and status.Every authorization check is done independently and in a certain order. In document management, the levels of the authorization check are:
1. Transaction code
2. C_DRAW_BGR
3. C_DRAW_TCD
4. C_DRAW_TCS
5. USER :Authorization object C_DRAW_BGR can be used to restrict access to individual documents. It works like a simple on/off switch. If the C_DRAW_BGR check does not find anything, the user's authorization can be further restricted by checking C_DRAW_TCD (checks the document type) or C_DRAW_TCS (checks the combination of document type and status).
Important T-Codes for DMS:
CV01N - Create Document
CV02N - Change Document
CV03N - Display document
CV04N - Find Document
CV11 - CREATE DOCUMENT STRUCTURE
CV12 - CHANGE DOCUMENT STRUCTURE
CV13 - DISPLAY DOCUMENT STRUCTURE
CV15 - CHANGE DOCUMENT BOM GROUP
KPRO - KPRO Administration Basis - Content Management Service
OACT - Maintain Categories Basis - Content Management Service
OAC0 - CMS Customizing Content Repositories Basis - Content Management Service
DC10 - Define document types Cross Application - Document Management System
CSADMIN - Content Server Administration Basis - Content Management Service
DC30 - Define workstation application Cross Application - Document Management System
DC20 - Define data carrier Cross Application - Document Management System
CORD - Batch Record: Type of dms Used PP - Production Planning for Process Industries
CVAR - Archive dms Tables Cross Application - Document Management System
CJ14 - Display WBS Element (From dms) Project Systems - Operative Structures
CVLO - Delete Archived dms Table Entries Cross Application - Document Management System
CN19 - Display Activity (From dms) Project Systems - Network and Activity
CN26N - Display Mat. Components (From dms) Project Systems - Material
CVW2 - Index search dms in WWW Cross Application - Document Management System
CVWG - dms: Test for up/download ActiveX Cross Application - Document Management System
S_BIE_59000018 - IMG Activity: dms_SKPROG KM - Knowledge Warehouse
S_BIE_59000028 - IMG Activity: dms_SKPR04 KM - Knowledge Warehouse
S_BIE_59000029 - IMG Activity: dms_SKPR02 KM - Knowledge Warehouse
OD41 - Global dms Settings Cross Application - Document Management System
Standard Workflow Templates:
00400225 - Create Draw For Image Document
16600160 - Period-end close cost object (hierarchy)
30100050 - ArchiveLink: Early+simult. archiv. 2
Following are the BAPIs available in SAP DMS:
BAPI | Description |
|---|---|
BAPI_DOCUMENT_CHANGE | You can change documents with this BAPI |
BAPI_DOCUMENT_CHECKIN | You can check in documents with this BAPI |
BAPI_DOCUMENT_CHECKOUTMODIFY | You can check out documents for processing with this BAPI |
BAPI_DOCUMENT_CHECKOUTVIEW | You can check out documents for display with this BAPI |
BAPI_DOCUMENT_CREATE | You can create documents with this BAPI |
BAPI_DOCUMENT_CREATEFROMSOURCE | You can create documents by copyi from a source document with this BAPI |
BAPI_DOCUMENT_CREATENEWVERSION | You can create document versions with this BAPI |
BAPI_DOCUMENT_DELETE | You can delete documents or set the deletion indicator with this BAPI |
BAPI_DOCUMENT_DEQUEUE | You can unlock documents with this BAPI |
BAPI_DOCUMENT_DISPLAY | You can display documents (without dialog) with this BAPI |
BAPI_DOCUMENT_ENQUEUE | You can lock documents with this BAPI |
BAPI_DOCUMENT_EXISTENCECHECK | You can check documents for their existence with this BAPI |
BAPI_DOCUMENT_GETACTVERSION | You can determine valid document versions with this BAPI |
BAPI_DOCUMENT_GETAPPLICATION | You can determine application data with this BAPI |
BAPI_DOCUMENT_GETDCDETAIL | You can determine the detail data of a data carrier with this BAPI |
BAPI_DOCUMENT_GETDCLIST | You can determine lists of data carriers with this BAPI |
BAPI_DOCUMENT_GETDETAIL | You can determine detail data for a document with this BAPI |
BAPI_DOCUMENT_GETDOCTYPEDETAIL | You can determine document type data with this BAPI |
BAPI_DOCUMENT_GETFRONTENDTYPE | You can determine computer front end types with this BAPI |
BAPI_DOCUMENT_GETLIST | You can search for/find documents with this BAPI |
BAPI_DOCUMENT_GETOBJECTSDOC | You can determine documents for an object with this BAPI |
BAPI_DOCUMENT_GETSTATUS | You can read document statuses with this BAPI |
BAPI_DOCUMENT_GETSTATUSLIST | You can determine status lists for document types with this BAPI |
BAPI_DOCUMENT_GETSTRUCTURE | You can determine document structures with this BAPI |
BAPI_DOCUMENT_GETTEXTS | You can read long texts for documents with this BAPI |
BAPI_DOCUMENT_SETFRONTENDTYPE | You can set the front end type for computers with this BAPI |
BAPI_DOCUMENT_SETSTATUS | You can set the document status with this BAPI |
Business Object Repository: DRAW
SAP and T.A.Cook Conferences are delighted to invite you to the International SAP Conference on Product Lifecycle Management taking place on 3-4 November 2016 in The Hague, Netherlands.
Request Brochure >l.jersova@tacook.com
This customer-centric, business focused event is specifically designed for discrete and process manufacturing organizations and will focus on enabling business leaders to leverage innovation and technology.
Join us to learn first hand from leading companies on how they have successfully managed end to end processes and product development more efficiently using SAP PLM solutions. Plus, get the latest from SAP on PLM solution innovations and strategy updates.
This international conference will be co-located as one of six in our SAP Conferences on Extended Supply Chain series including Supply Chain, PPM, EHS, EAM and Manufacturing. Registration for any one event will give you access to all six! Find out more >
For any inquiries, please contact the T.A.Cook event team at info@tacook.com or call +44 121 2003810.
All,
just wanted to share a quick heads-up: We will run a webinar series (German Language) on Product Lifecycle Management, prior to the upcoming SAP PLM Infodays. See below for topics, details and registration links.
If you are not aware of the PLM Infodays, go to Registration is open: SAP-PLM-Infodays in Walldorf, Germany - June 27-28, 2016
Best,
Arend
13. Juni 2016, 10.00–10.40 Uhr
SAP Document Center – einfacher und mobiler Zugriff auf sämtliche Dokumente
In diesem Webinar erleben Sie, wie der Zugriff auf Geschäftsdokumenten harmonisiert und vereinfacht werden kann. Mit der Lösung SAP Document Center können Dokumente aus unterschiedlichen Dokumentenmanagement- und bestehenden ERP-Systemen verfügbar gemacht werden. Der Einsatz moderner UI-Technologie ermöglicht den Zugriff auf Dokumente im Büro oder von unterwegs, sowohl online als auch offline.
13. Juni 2016, 13.00–13.40 Uhr
SAP Asset Intelligence Network – Equipmentportal für Hersteller
Das SAP Asset Intelligence Network bringt Hersteller und Betreiber in der Cloud zusammen – mit dem Ziel, Equipment-Daten standardisiert zur Verfügung zu stellen und physisches Equipment einheitlich virtuell zu repräsentieren. Dies bildet die Grundlage für weiterführende Kollaborationsszenarien aller Parteien. Erfahren Sie in unserem Online-Seminar, wie Sie von den zahlreichen Möglichkeiten der Integration und Erweiterung in die bestehende SAP-Landschaft profitieren können.
14. Juni 2016, 10.00–10.40 Uhr
Entwicklungsbegleitende Kalkulation mit SAP Product Lifecycle Costing
Lernen Sie in diesem Webinar die neue SAP-Lösung für den Bereich der Produktkostenkalkulation und die Angebots- und Entwicklungsbegleitende Kalkulation mit SAP HANA kennen. Mit dieser Anwendung lassen sich in der frühen Phase des Produktlebenszyklus Kosten strukturieren und abschätzen, aber auch Kostentreiber identifizieren und Alternativen darstellen. Die Lösung verbindet damit Entwicklung und Produktion.
14. Juni 2016, 13.00–13.40 Uhr
SAP PLM als Grundlage zur Digitalisierung in der Prozessindustrie
Hohe Wiederverwendung, Durchgängigkeit der Prozesse und Daten sind ein Schlüssel zum Erfolg eines Unternehmens bei der Produktivitäts- und Innovationssteigerung. Speziell in der Prozessindustrie ist eine frühe Compliance-Überprüfung maßgebend für eine gesunde Scale-up-Phase. Erfahren Sie in diesem Webinar, wie Sie Ihre Spezifikationen, Rezepte und dazugehörige Deklarationen mit SAP Recipe Development verwalten können.
21. Juni 2016, 10.00–10.40 Uhr
SAP Engineering Control Center: Die SAP-Strategie zur Integration verschiedener Autorensysteme
Das SAP Engineering Control Center integriert zahlreiche Autorensysteme in SAP PLM wie z.B. SAP 3D Visual Enterprise, Office-Software sowie verschiedene Arten von CAD-Systemen. Die Lösung hat eine vertraute Oberfläche und unterstützt eine einfache, intuitive Arbeitsweise selbst in komplexen Strukturen. Neben der Verwaltung von CAD-Modellen und Dokumenten bietet das Integrationstool weitere Funktionen, die wir Ihnen im Rahmen des Webinars vorstellen werden.
21. Juni 2016, 13.00–13.40 Uhr
Wie aus guten Ideen Wirklichkeit wird – Innovationen richtig angehen
Die richtigen Ideen erfolgreich umzusetzen ist eine Kunst. Unterstützung dabei bieten die Anwendungen SAP Innovation Management und SAP Portfolio and Project Management. Ideen werden damit gezielt gefunden und realisiert. Dabei werden die neuesten SAP HANA-Funktionen und intuitive UIs gebündelt, um Sie bestmöglich bei diesen Aufgaben zu unterstützen. Im Webinar beleuchten wir die Funktionen im Rahmen einer Live-Demo.
30. Juni 2016, 10.00–10.40 Uhr
Mobile Materialanforderung für Service-Techniker
Mit der „Mobilen Materialanforderung“ können Servicetechniker im Außendienst mit einem mobilen Endgerät dringend benötigte Ersatzteile suchen, deren Verfügbarkeit prüfen und diese bestellen. Einsatzmöglichkeiten für dieses Szenario gibt es u.a. bei der Reparatur und Wartung von Maschinen und Anlagen, voll integriert in Ihr SAP-Backend.
Today we were blocked from recreating indices for PLM search because of one broken ER in the system, the indexing short dumped while trying to close an ER with inconsistent sub-components. I tried all the standard methods, even tried to use /PLMI/CL_ECR_BO->DELETE_CHANGE_RECORDS without success. I then found out about BAPI_CASE_DELETE but even that wouldn't work because of the inconsistency with the ER in question. However, I ended up using BAPI_CASE_DELETE because that was the easiest to cheat around.
Disclaimer: do not attempt the following unless you know what you are doing. Even if you do, I do not take any responsibility if you happen to break your system by following these instructions. You have been warned!!!
Navigate from BAPI_CASE_DELETE to CL_SCMG_CASE_API->IF_SCMG_CASE_API~DELETE and then to CL_SCMG_CASE->IF_SCMG_CASE~DELETE. Locate the code which is checking each sub-component for authorization and place a break point following the call.
TRY.
READTABLE gt_subcomp_fcodes INTO wa_fcode WITHKEY fcode = <wa_subcomponent>-fcode.
IF sy-subrc = 0.
IF wa_fcode-classname ISNOTINITIAL.
ls_subcom_clas_method-clsname = wa_fcode-classname.
ls_subcom_clas_method-cpdname = 'CHECK_ACTIVITY_AUTHORIZATION'.
CALLFUNCTION'SEO_METHOD_GET_DETAIL'
EXPORTING
cpdkey = ls_subcom_clas_method
EXCEPTIONS
not_existing = 1
no_method = 2
OTHERS = 3.
IF sy-subrc <>0.
lb_activity_is_authorized = if_srm=>true.
* method CHECK_ACTIVITY_AUTHORIZATION does not exist..default auth to be true
*this may occur for subcomponents created by other appl & customer
CONTINUE.
ELSE.
TRY.
CREATEDATA lcl_subcomp_ref_var TYPEREFTO(wa_fcode-classname).
ASSIGN lcl_subcomp_ref_var->* TO<wa_subcomp_clas_instance>.
<wa_subcomp_clas_instance> ?= <wa_subcomponent>-class.
ls_string = 'CHECK_ACTIVITY_AUTHORIZATION'.
lcl_subcomp_obj ?= <wa_subcomp_clas_instance>.
CALLMETHOD lcl_subcomp_obj->(ls_string)
EXPORTING
im_activity = if_srm_document=>act_delete
im_skip_authorization = if_srm=>false
IMPORTING
ex_activity_is_authorized = lb_activity_is_authorized.
*--keep check as TRUE if the check_activity_authorization is not implemented by
*--component or the class is different.
CATCH cx_root.
lb_activity_is_authorized = if_srm=>true.
lb_activity_is_authorized = if_srm=>true.
ENDTRY.
ENDIF. " close of IF sy-subrc <> 0.
IF lb_activity_is_authorized = if_srm=>false. " <-- place break point here
MESSAGE s009(scmg_case)DISPLAYLIKE'E'.
RAISE EXCEPTION TYPE cx_srm_sp_client.
ENDIF.
ENDIF. " close of IF wa_fcode-classname IS NOT INITIAL
ENDIF. " close of IF sy-subrc = 0
CATCH cx_scmg .
RAISE EXCEPTION TYPE cx_srm_sp_client.
ENDTRY.
Whenever the execution reaches your break point, change the value of lb_activity_is_authorized to 'X'. At the end of the execution your inconsistent ER will be deleted and you will be able to create indices for PLM search.
While not pretty, the solution works. In my opinion there should be a standard report to either repair ERs or delete them if they are beyond repair.
SAP presented the new product costing solution at the SAP PLM Infodays 2016 taking place on 27th–28th June in Walldorf/St. Leon-Rot. About 230 interested customers and partners participated in this event with the focus topic “Product Lifecycle Management as key enabler for an agile and customer–driven enterprise” , joining from as far as China and the US.
On the first day the attendees could listen to keynotes which were presented by SAP and customers like Kion and Unilever to learn how the “Digital Twin” can help companies to digitize their value chains. Furthermore SAP presented in several breakout sessions new solutions and business models for the future.
Ulf Petzel presenting “Optimization of Quotation Costing and Preliminary Cost Estimates”
On the second day our customers and partners could inform themselves in two deeper dive sessions about the extensibility framework & analytics and options to fast track implementation of PLC. In the first session Daniel Oberle and Matthias Walter showed how easy other applications can be called up using the add-in framework. Later on the configuration, set up and implementation with other tools that have been made available to support a fast-track approach were in the focus of the second session.
Join this intense 3-hour session, which will examine the continued expansion of the SAP Product Lifecycle Management (SAP PLM) application portfolio, will delve into the various ways its functions can be used to meet critical business process requirements, and will explore how it meets the needs of your integrated enterprise.
This is your chance to:
The session will run from 9:00 till 12:30 on 3 November in The Hague, Netherlands and is a part of the International SAP Conference on Product Lifecycle Management.
For more information please click here.