this works on my case too, thank you
AT
this works on my case too, thank you
AT
>>trc file: "D:\usr\sap\GS1\JC00\work\dev_jcontrol", trc level: 1, release: "700"<<
>>[Thr 4216] *** ERROR => OS release Windows NT 6.1 7601 Service Pack 1 4x AMD64 Level 6 (Mod 62 Step 4) is not supported with this startup framework (700) [jstartxx.c 4389]<<
Replace the kernel with a higher release and start the SAP manually from SAP MMC
Regards
RB
On my current client, we have a unique business scenario where we need to maintain GR processing time to reflect "incubation or hold" time for products after production. It is absolutely necessary that the products should not be available to ship to the customers until this "incubation or hold" time is elapsed and the products are inspected & ready for customer shipments. However, the products can be shipped to other DCs within the client's internal network while the products are under "incubation" as it can take place while the products are in-transit. Therefore, the products are available for shipping immediately after production within the client's internal network of DCs. This is why we need a mechanism to ignore the GR processing time while the products are shipped on STOs within the network. At the same time the GR processing time should be considered while the products are shipped against customer SOs outside the network.
To explain the scenario a bit further, this is a simple scenario: Factory A --> DC1 --> DC2. Factory A produces products to be stored and DC1, which ships to its own customers as well as to DC2 to fulfil customer demand at DC2. "Incubation" time of products is performed in DC1. Therefore, Sales Orders at DC1 should not be able to ship until this "incubation" time has elapsed at DC1. This can be accomplished by maintaining GR processing time equal to "incubation or hold" time at DC1 and it works well for Sales Order and its Delivery ATP check. On the other hand, STOs from DC1 to DC2 can ship immediately after production while the product is still under "incubation" as the required hold time can elapse while the products are in-transit between DC1 and DC2. Therefore, STO & its Delivery ATP check should consider production from factory A to be immediately available after production. Note that the incoming production from factory A is represented by an STR between factory A and DC1. Per my research this functionality is not available in standard SAP as GR processing time is considered in ATP check for both SOs and STOs. However, if anyone knows of a way to separate out ATP check for SOs and STOs where SO considers GR processing time while STO does not then that would greatly help.
Appreciate any suggestions or solutions.
Regards,
Jagjeet.
Hi Prasanth,
These links will also be useful: Automatically split indicator - ERP Financials - SCN Wiki and rounding off and the group condition in this document.Round off Condition Values - Pricing Configuration
Regards,
Unnivel
Hi
I would go by Sandy's and Rick's response ... to check the Auths of WF-BATCH user as these can be different in the systems, rest are same - WF, Binding, code, etc.
if you are calling RH* FM's in agent determination, the issue is most likely caused by auth's of user WF-BATCH.
Regards,
Modak
Hi Satish,
The error message indicates the assertion valid validation which is typically due to the private key used to sign the assertion not being compatible with the certificate used to validate the assertion.
Thanks,
Bo
Hi Girish,
I assume you have the Archive link ID. First the file contents from archive link then convert it in Xstring format and finally attach to Vendor GOS object.
Use the following FMs:
Refer to SDN thread
Attach files to GOS with Save, Retrieve, Delete functionality in SAP Web Dynpro ABAP - Part 1
Regards
Sandy
Hi Brhamma,
Shouldn't the java ports be 5xx00 and 5xx01 for http and https respectively, where xx is the system number?
Regards,
Mark
Hi All,
I am trying to learn Web dynpro FPM. I have NW7.3, but all the learning tutorials I could get are for NW7.0 and the configuration screen is very much different from the NW7.3.
As I am a beginner I am finding it very difficult to understand. Could you please share with me if anyone has any tutorial for NW7.3 or advise me how can I be able to learn.
Thank you for your time.
Hi Lawrence,
Thanks for your kind words.
I would still believe "\u" definitely causes the error and it does not rely on other factors.
(Mostly due to the fact that I'm saying this remotely.. Besides that, we are not involving dynamic factors like network, racing, etc)
Afaik, the config.properties file comes with guilty "\u" after installation.
Indeed under this case it's unwise for PcdCheckTool to read it via Properties.load() method.
Nevertheless if you ever change the connection property in configtool, the "\u" will automatically become "/u", and issue won't occur.
Otherwise you have to change "\u" to "/u" or "\\u" manually.
In contrary, configtool (7.3 +) reads "\u", "/u" and "\\u" perfectly. Why?
Configtool implemented its own method to avoid this IllegalArgumentException. (checked on 7.3)
(It was also using Properties.load in earlier releases)
Perhaps it's because configtool is much more popular than PcdCheckTool.
BR, Tom
Hi Sriram,
For logon data, you can compose the URL like this:
http://<host>:<port>/irj/portal?j_user=<username>&j_password=<password>
You can post other data as query string similarly.
But out of curiosity, why do you have such requirement?
You have to set a URL for every user?
How about SPNego, SAML or HeaderVariable authentication?
BR, Tom
Hi luke,
thank you for sharing the document
rgds,
Hilmawan
Hi DB,
Thanks for your answer!!!
The key was the "no storage location inspection". Now, the ATP is showing the correct qtys.
I'm going to comment this to my client, but I'll not recommend to do that due the inconsistences that could happen.
Regards.
Diego.
Hi Stacy,
A bit tricky to achieve what you are trying. But give this a try
Page 1
Main window
Loop 1 - For item details
Table - For material characteristics
Header
Main
Folder 1*
Line Type - for Item Header & Data
Line Type - for Material Characteristic Header
Line Type - for Material Characteristic Data
Command node for page break
* - Checkbox related to pagebreak settings checked only at folder and not at other rows/ line type
Regards,
Pulkit
Hi Amrit,
RFC Destinations are required to connect PI to SAP or SAP to PI systems.
For instance,Idoc and RFC scenarios.
Cheers,
Giri
Thanks Avinash - Note seems not to be relevant for us.
Regards
Dev
Hi Cleo,
If your Z table created is in reference to any master data/Transactional data(standard table) and if the keys match for the same, you could make a join using views and then use the view to extract delta(using the changed and created date information of the standard table) as a concept of Psuedo delta.
Regards,
Thejas K
Hi all,
we are getting below issue while registering secondary,
after opening all the ports starts with 300**
error: remoteHost does not match with any host of the source site. all hosts of source and target site must be able to resolve all hostnames of both sites correctly
failed. trace file nameserver_10.104.152.11.00000.000.trc may contain more error details.