Configuration materials for MM

Hi sap experts..
gud noon to all, can somebody help me ..
Actually i need some configuration documents for SAP- MM,(A to Z, step by step documents).
Kindly send me some Configuration documents.
my id [email protected]
Get the rewardable points by replying..
thanks
sap-mm

Hello sap-mm,
Please, do not ask to send the answers to the questions by e-mail.
The solution you are requesting might also be interesting for other users of the community. Sending the answer per email deprive others of also learning the relevant information.
Thank you in advance for your cooperation and understanding.
Best regards,
Esther Hernanz,
MM SDN forum moderator.

Similar Messages

Alternate Lot Sizing for KMAT (configurable) materials

Hi friends,
We are using KMAT(configurable) materials.
During MPS/MRP run, SAP plans KMAT production with Lot-to-Lot production(EX) by default!
We have some capacity planning situations, due to which, we need the lot sizing options like u2018Fixed lot (FX) sizeu2019 or u2018Fixed lot size with splitting(FS)u2019 or even use of u2018Min-Max lot sizeu2019... so that the large requirements are transferred in smaller lots to the plant.
But, when we use any of these lot- sizing procedures in MRP1 screen of the material master, we do not find any difference in MRP resultsu2026 system just triggers the planned order exactly matching the Sales order quantity (as if we still use EX)!
SAP notes 437098 and 724235 hint that the alternate lot sizing procedures are possible to set up for configurable materials... but we are struggling to crack this.
If any of you have had an opportunity to work on alternate or custom lot sizing procedures with KMAT (configurable) materials, it would be wonderful to hear the suggestions and results.
Thanks in advance.
Best Regards,
Senthil

Hi Dario,
Thanks for the response.
We use ECC6.0; I could not find the inidicator you've referred (customer requirement)... in transaction OMI4 : Check Lot Sizing Procedure --> MRP Lot Size...
Kindly advise if you were referring to any other version or any other transaction...
Best Regards,
Senthil

Error message while creating configurable material for variant configuration.

Dear All,
I want to create configurable material for the purpose of variant configuration. When trying to create configurable material using mm 01 or mm k1, it is displaying an error message that internal number assignment is not possible for the material type configurable materials as well in using external number also. Can anyone specify the steps to be done in creating the configurable material. Thank you all.
Regards
Akula Sivaji Kumar Madhu Kiran

If you want to set these material type to another group (Which has a internal number and external number range), then you can do it.
In MMNR, Click on the Edit Group.
Then select the material type and click select element.
Then mark a tick option in another group and then press Element/Group.
Then you can see the material type will come under this group.
Now save your entry, and create a material with this material type.

Non-configurable materials with EK02 costing

Hi all,
We have a range of non configurable manufactured materials which, when used in standard sales orders, generate a production order and BOM. Presently the cost is automatically generated from the material master and is populated as a VPRS cost.
As these materials have a BOM we want the cost to pick up from the BOM instead, ie as an EK02 cost. If we enter such a material and do a manual recost the EK02 populates in the sales order item conditions but we cannot get it to populate automatically as it does with configurable materials with BOMs.
In the define item categories section in SPRO we have removed the determine cost tick. This has the desired effect of removing the VPRS cost but the EK02 cost still doesn't pull through. In the Bill of Material / Configuration section of the item category we tried setting the structure scope to A (Explode single-level bill of material) and B (Explode multi-level bill of material) but this didn't work. If we set it to D (Configuration, poss. with BOM explosion), then we get the "item can be configured but there is no configuration" error when used in a sales order which is expected as these products have no configuration.
We also tried deleting the standard cost held in the material master to see if, as that value was now blank, it would pick up the EK02 instead but, alas, this also ddn't work.
Any help / suggestions would be most appreciated.
Kind regards, Rob

HI,
We are maintaining the Service masters for the services we render, there is no valuation of Inventory as only service is being rendered.
But we have maintained BOM and Routings for the services we render.
Even there is no valuation class in the serivice masters as this is non valuated.
Can you guide me more on this pls.
Thanks,
Ravi

Blocked field in Sales Order when using configurable materials

Hi everyone,
I have noticed that every time I insert a configurable material in a Sales Order Line, after pressing ENTER and having valuated the associated characteristics, the Material and Position Type fields stay blocked so I cannot change the material in this position.
According to the process I am implementing, I would need in certain cases to change the material (replacing the configurable for a non-configurable one).
I would be very grateful if someone could help me to avoid that these fields get blocked or at least to know the reason.
Thanks in advance and best regards.
Ben.

I don't have any experience with configurable materials, but it seems that in this case you'll need to delete the line (or the lines) and re-enter them with the proper type of material.

How to configure rescheduling for sale order quantities

kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumar

Hi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO        4500000012      10               0001              26.01. PO        4500000012      10               0002              26.02. PO        4500000025      20               0001              28.01. PO        4500000025      20               0002              02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat.    Doc. number Doc. item Doc. sched. line Del. date PO           4500000012    10             0001           26.01. PO           4500000025    20             0001           28.01. PO           4500000025    20             0002           02.02. PO           4500000012    10             0002           26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity   Confirmed quant Confirmed del. date 23.07.      50 items       0 items              -
==> This now affects the stock/requirement situation:
    - Goods issue is posted for the material in the delivering plant on the 23.07.
    - A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity   Confirmed quant   Confirmed del. date 23.07.     40 items      40 items            23.07. 29.07.     10 items      10 items            29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
   Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07.     10 items       10 items          29.07. 30.07.     40 items       40 items          30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit

Variant Configuration Materials Costing Scenario

Hi All,
Any one explain me Variant Configuration Materials Costing Scenario in descrete manufacturing?
any help is appreciated.
Thanks,
Anusha

Hi,
Can any one explain me step by step configuration in Controlling(CO) for Variant configuration materials? and Explain me process steps in Controlling(CO) module for variant configuration?
Any help is appreciated.
Thanks,
Anusha

Materials for sap configuraion

hi,
i want to configure bw system with other systems where can i get materials for that.

Hi Sanjay!
take a look to OSS Notes 184971 'Notes on BW source system connections' and 184447 'Building BW System Landscape' and 192658 'Setting Basis Parameters BW Systems'
Hope it helps!
Bye,
Roberto

Configuration values for a planned order

I want to create a plan order for configurable material and want to assign characterstic values.
But all the configuration data is grayed out , so can some one tell me what I need to change to enable value assignment at plan order level?
thanks,
Husain,

Hi Husein,
You can not create planned order manually for configurable material. The characteristic for configurable material is taken from sales order. When you run MRP for sales order, planned order will be created for this order. If you maintain variant where you determined the characteristic previously in MRP 3, you can create planned order this material variant. Remember maintain strategy planning with make to stock.
Other way you should use IS MILL.
Here some brief from help :
In SAP Mill Products you can manufacture configurable materials and material variants with production orders not only with reference to sales orders but also for stock. You can also change the characteristic value assignments of a material variant in production orders.
Prerequisites
The following requirements must be fulfilled in order to manufacture configurable materials and material variants for stock.
·         Your SAP R/3 system must be linked to a SAP Advanced Planner and Optimizer (SAP APO) system because characteristics-based planning is only possible in SAP APO.
·         The configurable material or the material variant must be contained in an active integration model.
·         The material must be managed in batches so that warehouse stocks of materials with different characteristics can be distinguished.
Regards,
Arman

Creating Materials for the Header items and component items

Hi MM Experts,
I am doing configuration for the KIT items Sales Processing.
For that I need to create Materials for Header materials & component materials in MM01.
I need few inputs regarding for this:
What Material type ,I should give for the header material and component material in MM01?
What Item category should used for these Header & components items in the Sales Order ?.
I am using a Price at Header Level ,so will TAQ suffice me for the Header item ??
Do i need to maintain separate condition records for the Header material and all the item materials in
VK11 ?
Thanks for your answers in advance.
Thanks and Regards,
Umesh Karane.

Hi
Any material type... depending on your requirement Normally Finished product.
Item category Normally use NORM, if u want to use third party slaes then use BANS
Check it out
Regards,
Raman

Variant Configuration / Need for a separate forum

Dear Moderators,
I have been contributing, accessing and extracting information from this forum for my projects and trainings. Recently we have added lot of new forums especially in SD, a separate forum for billing, sales etc.
On the same path, I feel that it will add immense value if a new forum for Variant Configuration is created. As this is an area which touches various modules, and various applications like configurable materials in SD, Release procedures in MM, etc, people can share all the information regarding variant configuration in a common forum like this.
May I please request you to consider this and take it forward if this makes some sense.
Any feedback on this is welcome, especially from people like Rajesh Banka, Laxmipathy etc who have been here for quite sometime in SD

I'm going to respectfully disagree.
I saw something similar at elementsvillage.com when they created a "Mac-Specific" forum. People who had questions that really had nothing to do with their Mac, for example "Can't open RAW from D7000", still put the question in the Mac-Specific forum, because they were using a Mac. As a result, the community was fragmented in ways that had nothing to do with the question. People who might have benefited from this question but didn't have a Mac and so didn't look in the Mac-Specific forum, and didn't get the answer as quickly. People who asked questions in this forum that had nothing to do with Macs wound up relying on a smaller community of experts to help solve the problem. I know I certainly never read that forum, so I didn't provide answers, nor did I learn from the information in that forum. I consider that decision to create a "Mac-Specific" forum to be a failure.

My total process is mto process, all materials configurable materials ,

hi
i am working steal company ,
my total process is mto process, all materials configurable materials , its bases on characteristic , how to configure the r/3 and apo , what is the main parts and settings , how trigger the global atp with based on characteristic , and what configurations
how to create the production order,
i create the 10 sale orders with one production order , how to configure this , what are the settings needs, how to system internal settings
please help him
regards
sankar

Sankar,
It is contrary to forum rules to place email addresses in posts.
Creating a new implementation for APO is not a trivial matter. Most companies will hire a consulting company experienced in such matters to assist them.
However, if you wish to tackle this yourself, a good starting point for documentation is Best Practices. Your business requirements are unclear, but I will assume you wish to configure Global ATP, and I will further assume you wish to implement some kind of planning (either PP or SNP). Here are the required modules:
Connectivity
http://help.sap.com/bp_scmv250/BBLibrary/HTML/B02_EN_DE.htm
Replication
http://help.sap.com/bp_scmv250/BBLibrary/HTML/B05_EN_DE.htm
GATP
http://help.sap.com/bp_scmv250/BBLibrary/HTML/ATP_EN_DE.htm
PP
http://help.sap.com/bp_scmv250/BBLibrary/HTML/S16_EN_DE.htm
SNP
http://help.sap.com/bp_scmv250/BBLibrary/HTML/B06_EN_DE.htm
For general info about GATP, refer to SAP help
http://help.sap.com/saphelp_SCM700_ehp02/helpdata/en/04/5e7237412a5249e10000009b38f842/frameset.htm
Best Regards & Good luck,
DB49

Inventory Turnover with Configurable Materials (i.e. KMATs)

Dear Experts,
Has anyone developed inventory turnover reporting that involves configurable materials (i.e. KMATs)?
I have a situation where the client wants to report inventory turnover at the plant level. A plant issues both stocked goods and configurable materials (i.e. assemble to order) to customers. Unlike stocked goods, configurable materials do not carry standard cost and are costed during sales order settlement at month's end (i.e. material movements for KMATs are not valuated).
In order to determine Cost of Goods Sold (since Inventory Turnover = Cost of Goods Sold / Average Inventory), I suppose that Cost of Goods Sold would be equal to the sum of the issue value of stocked goods plus the issue value of configurable materials (i.e. ATOs).
SAP Business Content provides InfoCube 0IC_C03 for Material Movements (and likewise Inventory Turnover reporting). The delivered content supporting this InfoCube deals with valuated stock only (by looking at material movements). Valuation for KMATs cannot come from material movements (since the material movements of KMATs are non-valuated). Since the SAP Business Content scenario for Inventory Turnover does not provide an apparent mechanism for loading the cost of goods sold for configurable materials, I'm beginning to wonder if I have this all wrong.
Does it make sense that configurable materials would be included in inventory turnover calculations at the plant level? Even though the ATO itself is not stocked, the components are, and there is a cost associated with carrying those components (and also selling them as part of the ATO). Should I be looking at the cost of goods sold for the ATO or is there a way to valuate the cost of the components sold as part of the ATO simply by considering material movements for those components?
Any thoughts on this one? Did I even make any sense?
Thanks,
Jim

hi,
thanks indeed for the reply.
but here i have to enter characteristics details for every catalog number assoiciated with particular material. i tried this too but still getting the Item Gross Price as zero only. for other condition records too, getting this zero value.
do you have sample code for this?
is there any alternative for that? any other function module i can use?

Error trying to configure ADS for printing from BW reports

hi all,
i am trying to configure ADS for printing off reports from the BW portal. I am using BI 7.0 (BW Portal version 7.0 SP10) and am getting the following error i nthe default trace file.
#1.5#00187177BCAA008D000000DD0000144C00043EE522456586#1195053750220#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1678##BWD#PASS.TEST                       #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
     at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
     at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
     at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
     at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
     at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy145.processFunction(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
     at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
     at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
     at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
     at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
     at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
     at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
     at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
     at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
     at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
     at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
     at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
     at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
     at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
     at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
     at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
     at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
     ... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
     ... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
     ... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
     ... 46 more
#1.5#00187177BCAA008D000000E00000144C00043EE522456FA1#1195053750220#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1678##BWD#PASS.TEST                       #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException
Log ID: 00187177BCAA008D000000DD0000144C00043EE522456586
Initial cause
Message: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
Stack trace: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
     at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
     at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
     at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
     at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
     at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
     at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
     at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
     at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
     at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
     at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
     at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
     at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
     at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy145.processFunction(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
     at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
     at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
     at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
     at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
     at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
     at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
     at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
     ... 46 more
Message: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
     at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
     at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
     at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
     at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
     at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy145.processFunction(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
     at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
     at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
     at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
     at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
     at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
     at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
     at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
     at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
     at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
     at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
     at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
     at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
     at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
     at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
     at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
     at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
     at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
     at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
     ... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
     ... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
     ... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
     ... 46 more
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException#
#1.5#00187177BCAA0084000000120000144C00043EE523772516#1195053770252#com.sap.ip.bi.export.xfa.impl.PDFConverter#sap.com/irj#com.sap.ip.bi.export.xfa.impl.PDFConverter#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###EXPORT XFA calcTemplate=Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out#
#1.5#00187177BCAA0084000000130000144C00043EE523772FEE#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###Exception caught: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
     at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
     at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
     at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
     at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
     at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
     at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
     ... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
     ... 53 more
#1.5#00187177BCAA0084000000140000144C00043EE523773518#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
     at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
     at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
     at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
     at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
     at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
     at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
     at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
     at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
     ... 49 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
     ... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
     ... 53 more
#1.5#00187177BCAA0084000000170000144C00043EE5237744D3#1195053770252#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/irj#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001#

Hi Glenn,
i faced the same problem
did you solve yours meanwhile ?
regards,
Carsten

The boot configuration data for your Pc is missing or contains errors: error code 0x000014c

Hello,
See if any body may help here... I get this blue screen:
RECOVERY
Your PC needs to be repaired:
The Boot Configuration Data for your PC is missing or contains errors.
file:\\EFI\Microsoft\Boot\BCD
Error code: 0xc000014c
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a a disc or USB device), contact your system administrator or PC manufacturer.
Press Esc for UEFI Firmware Settings
First I was able to get into the option 11 and run the whole factory reset, i was so happy because I tought it will be easy.. but then after I did the factory reset.. I keep getting this blue screen. if I press ESC I get into this next screen:
F1 System Information
F2 System Diagnostics
F9 Boot Device Options
F10 BIOS Setup
F11 System Recovery
ENTER - Continue Startup.
this is what happen when I click any of this options:
F1 I get into the System Information with no problems, then I click <ESC> to continue and get back to the last screen... then I press F2 and super, I am able to run Memory Test and Hard Drive Check 100% with no problems in any of those, after I am done with my teste I press exit and I am back to the F1,F2, ETC menu... now I want to try F9, F10 or F11. bummer.. in this 3 options I get back to the blue screen described at the beggining of this post. (I already connect a USB with an boot loader, which works perfectly)
so I can't do anything, nothing at all!! crazzines.
So what I did to check why I can't get into the BIOS or at least to boot from my USB... I removed the botton cover of my laptop and removed the hard drive and that's how then I was or I am able to Log into the BIOS, - I did the changes to boot first from the USB and then from the HD and this is how I was able to boot from the USB - BUT If I connect back the Hard drive, I am not able to get into the BIOS or boot from the USB - so basically I am stuck in this blue screen and I can't boot from a USB if I have the HD connected.. I can't use any option.. no BIOS, nothing.. only if again, i disconnect the HD.
This is an:
HP ENVY TS Sleekbook 4
PRODUCT NUMBER D1A99UA#ABA
SYSTEM BOARD ID: 1894
Bios F.25
**** I though that by updating the BIOS I may be able to get help, nothing. What I did is, I removed the HD and then and boot from the USB and with a DOS command propmt I excecuted the Bios Update from F.21 to f.25... but again, when I installed the hard drive back, BUMMER, nothing I can't do nothing but this silly blue screen.
Any idea of what should I do?
Thanks in advance.
This question was solved.
View Solution.

If you can't access BIOS with the hard disk connected, you certainly won't be able to boot to the usb recovery flashdrive. That is indicative of a failed hard disk.
Install a new hard disk and then boot to the recovery flashdrive.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Configuration materials for MM

Similar Messages

Maybe you are looking for