Shipments of fronthaul optical transceiver (OTRX) modules declined in 2016, mirroring the trend in remote radio unit (RRU) shipments, and will bottom in 2019, awaiting the growth of 4.5G, 4.9G and 5G to pull the industry into its next growth cycle, according to market analyst Earl Lum. https://goo.gl/ydTXYJ #5G #IoT #5GWorld
Enable and troubleshoot Monitor production orders, Manage orders, Manage PIR, Internal order apps
This blog will help you in enabling and troubleshooting the below apps in S/4 HANA 1610 FPS01
* Monitor Production Orders
* Manage Orders
* Manage PIR
* Internal order
Monitor production orders, Manage orders, Manage PIR, Internal order
Steps to enable
* Ensure the software component UIS4HOP1 200 – SP 0001 is installed. UIAPFI70 400 – SP 0001 for Internal order factsheet app
* Ensure the backend component S4CORE 101 – SP 0001 is installed.
* Enable the below SICF services
* PP_PRDORDI_MRS1 (for monitor production orders)
* PP_MRP_REUSES1 * (for monitor production orders
* PP_FCDMISSUESS1 (for manage PIRs)
* FIN_FS_INTORDER (for internal order)
* Enable the below ODATA services
* PP_MRP_COCKPIT_SRV 0001 (for monitor production orders)
* PPH_FCDM_MAINT_SRV 0001 (for Manage PIRs)
* CB_INTERNAL_ORDER_SRV 0001(for internal order)
* Enable the WDA application EAMS_WDA_ONL_IC_OVP for Manage orders
* For Manage PIRs
* Assign the business roles SAP_BR_PRODN_PLNR and SAP_BR_MATL_PLNR_EXT_PROC to
* the business catalog SAP_SCM_BC_FCDM_MAINTAIN
* the business group SAP_SCM_BCG_MATL_PRODN_PLNG
* Assign the respective users to the business role SAP_BR_PRODN_PLNR and SAP_BR_MATL_PLNR_EXT_PROC
* For Monitor production orders
* Assign the business role SAP_BR_PRODN_PLNR to
* the business catalog SAP_SCM_BC_PLNG_INH_PRODN
* the business group SAP_SCM_BCG_MATL_PRODN_PLNG
* Assign the respective users to the business role SAP_BR_PRODN_PLNR
* For Internal order
* Assign the business role SAP_BR_CONTROLLER to
* the business catalog SAP_SFIN_BC_CO_FS_OPA
* Enable the below search connectors
* INTERNAL_ORDER_H
* SYSTEM_STATUS
* CONTROL_DOC_UJE_H
* COST_CENTER_H
* COST_ELEMENT_H
* ASSET_H
* GL_ACCOUNT_H
* CUSTOMER_H
* WBS_ELEMENT_H
Troubleshooting
Issue 1:
* Go to Monitor production orders
* Enter the filter criterias
There may not be any data loading though there is data in the backend. The possible reasons are, the materials that are marked as bad will not appear in MRP apps. Inspite of having the materials as good, if the orders are not loading, running the report PPH_MRP_SET_CACHE in the respective backend system and make a buffer refresh using function “refresh for all selected entries” for the required plant and MRP controller will help in resolution.
Issue 2:
* Go to Monitor production orders
* From the list of orders displayed, choose an order of type ZPME
* Click on Manage items from the bottom right corner
This will not open the order, instead it will display “No items currently available”. This issue can be resolved by apply the note 2514888
Issue 3:
* Go to Manage PIR app
* Enter a material no and search
This will not display the results though the data is available in the backend and the if the same material no is searched from the Change PIR app, it will display the results.
The reason could be that the material uses the period type ‘P’. This is not supported in Manage PIRs. It supports only ‘M’ or ‘W’ as period types. Ensure that the area of responsibility is yours. Also, ensure that the authorization object M_FCDM_ORG with ACTVT=03 for display and 01 and 02 for change authority.
Also, it is recommended to always start with Manage PIRs and use it rather than using Create PIR / Change PIRs app.
Issue 4:
* Go to Internal order object page
* In the search results page, click on to the Display CO Production Order link which is there as part of each internal order search result.
This will throw an error Could not open app. This issue can be resolved by applying the notes 2496794, 2551251.
Hope this helps http://bit.ly/2Eiz0FS #SAP #SAPCloud #AI
Master handling Date/Time in E2E Fiori Scenario – Index
Generally handle with Date/Time data is a common skill for all developers.
But when you starting to develop Fiori applications, it gets far more complex than you think.
In a typical Fiori development scenario, different technologies are involved, they are ABAP, OData, and SAPUI5. There will be more backend languages involved if you use SAP Cloud Platform or other backend technologies.
In this series blog, what I want to do are:
Point out possible questions about Date/Time data.
Give the answer based on S/4 HANA scenario by examples and reference to SAP’s documents.( That means ABAP plays the backend role)
Help developer using other languages as the backend service to get the idea of how to figure out Date/Time problems in their own development scenario.
Blogs in this series planned ( with planned date ) are list below:
*
Identity Requirements for Date/Time operation(Plan: 2018-1-13)
*
How ABAP deal with Date/Time(Plan: 2018-1-20)
*
Conversion of ABAP Date/Time type to OData Date/Time type(Plan:2018-1-27)
*
How SAPUI5 deals with OData Date/Time(Plan:2018-2-3)
*
How to handle the representation of Date/Time in SAPUI5(Plan:2018-2-10)
*
Handling create request for entity with Date/Time fields(Plan:2018-2-17)
*
Handling entity which has Date/Time key field(Plan:2018-2-24)
*
Using Date/Time field as OData Query Option(Plan:2018-3-3)
*
Dealing with Time Zone and Time Difference(Plan:2018-3-10)
http://bit.ly/2EcIv9j #SAP #SAPCloud #AI