Mandatory field 'Reason for Delay" required in VKM3 Tcode application

Hi to all
We use tcode VKM3 to release the sales order for which credit limit check does not required.
Our requirement is to add a mandatory field 'Reason for delay" so that we can write in that field what's the reason to releasing it through VKM3.
Please guide me how to fullfill that requirement.
Thanks & Regards
Anubhav Gupta

Hi Anubhav,
Refer to the following very useful link:
Re: Add new fields to VKM3 transaction
Hope it helps.

Similar Messages

I want to know Reason for delay in activation of ODS

Hi,
I am using 3.x ver. normally ODS activation took 21 - 30 mins to activate but sometimes it took 6-8 hrs to activate.
for eg.
Yesterday it took 21 mins to activate 9,24,033 records and it added records were u201C1847245u201D but to day it took 8 hrs 13 sec to activate 877,560 records and it added u201C3507974u201D.
I checked the server also at that time server had not too much load.
This job started at 07:13 and finished at 15:26.I checked job log also.
07:13 SQL-END:22:08:2009 07:13:40:00:00:27
15:26 Activation start at 07:13:40
15:26 Activation finished at 15:26
15:26 Request.......
15:26 Request.....
15:26 Data pkgs.......
could you please help me to findout the reason for delay in activation of ODS. I am not able to findout what happened in first two lines in above job log.
Thanks,
Manish

Hi Manish,
When you want the resolution, you should have answered the quetion made by Markus Doehr, He such a qualified consultant you did care to follow up your issue.
Thank you,
Prasaad

EM Jobs Service is down (fatal). Reason - "Reason for delay could not be determined"

Hi all -
I'm having a problem with my em jobs service. It's listed as down. Severity is "Fatal". For the incident creation DATE it has the following:
"Reason for delay could not be established."
Note that it's the DATE column where it ways that the reason could not be established. Under "message" it has Dec 28, 2013 8:46:29 PM.
Target Name
Target Type
Severity
Message
Incident Creation Date
Incident Last updated Date
Escalation Level
EM Jobs Service
EM Service
Dec 28, 2013 8:46:29 PM
Reason for delay could not be established.
Jan 27, 2014 7:48:44 PM
None
Does anyone have any clue as to why this is happening and/or how to fix it?
Thanks,
Tom

Hi,
Follow the below steps
1. Click on Repository Database Target in Cloud Control
2. Navigate to : Administration -> "Oracle Scheduler" -> Home -> click on "Oracle Scheduler" it will return, "Scheduler Jobs"
3. Check that the scheduled jobs are running at their correct schedules. Check if the "EM_JOBS_STEP_SCHED" job is disabled.
4. Select "EM_JOBS_STEP_SCHED" and click on "Edit job Definition" ensure that the job status is "enabled". Then click apply.
5. Check the "EM Jobs Service" status , it should now be shown as UP.
Also
1. Login to 12c Console, Targets --> All Targets --> EM Jobs Service
2, click on Monitoring Configuration tab
3. click on System Configuration
In the Availability Definition screen, under Key Component column, check all the check boxes
4. Similarly, in the System Configuration screen, under Key Component column, check all the check boxes
Wait for 5 minutes and then check the status of the target again.
Regards,
Rahul

How to enable field "reason for rejection" of view "status" in CRMD_ORDER

Hello Everyone
I need to activate/enable field "Reason for Rejection" in view "Status" of transaction CRMD_ORDER though a delivery document is created for the sales order.
Can some one pls let me know where do I need to code to make field "Reason for Rejection" enabled.
FYI, the same logic was applied for VA02 as well and the logic is written in userexit "USEREXIT_FIELD_MODIFICATION" which is working fine.
Apprecriate your quick response.
Thanks
Dharma

Hi Raj,
Usually we use function module CRM_STATUS_UPDATE to
change user status in document. But if you want to
trigger next process or change from certain user status to next status interactively by the system, you can
use Badi CRM_ORDER_STATUS (here you have after and before
method).
Hope this could help.
Rgds,
Gun.

What could be the reason for continuous Full GC's during application startu

What could be the reason for continuous Full GC's during application (webapplication deployed on tomcat) startup?
JDK 1.6
Memory settings
-Xms1024M -Xmx1024M -XX:PermSize=200M -XX:MaxPermSize=512M -XX:+UseParallelOldGC
jmap output is below
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 1073741824 (1024.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = 17592186044415 MB
OldSize = 5439488 (5.1875MB)
NewRatio = 2
SurvivorRatio = 8
PermSize = 209715200 (200.0MB)
MaxPermSize = 536870912 (512.0MB)
Verbose GC logs
==========
0.194: [GC [PSYoungGen: 10489K->720K(305856K)] 10489K->720K(1004928K), 0.0061190 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
0.200: [Full GC (System) [PSYoungGen: 720K->0K(305856K)] [ParOldGen: 0K->594K(699072K)] 720K->594K(1004928K) [PSPermGen: 6645K->6641K(204800K)], 0.0516540 secs] [Times: user=0.10 sys=0.00, real=0.06 secs]
6.184: [GC [PSYoungGen: 262208K->14797K(305856K)] 262802K->15392K(1004928K), 0.0354510 secs] [Times: user=0.18 sys=0.04, real=0.03 secs]
9.549: [GC [PSYoungGen: 277005K->43625K(305856K)] 277600K->60736K(1004928K), 0.0781960 secs] [Times: user=0.56 sys=0.07, real=0.08 secs]
11.768: [GC [PSYoungGen: 305833K->43645K(305856K)] 322944K->67436K(1004928K), 0.0584750 secs] [Times: user=0.40 sys=0.05, real=0.06 secs]
15.037: [GC [PSYoungGen: 305853K->43619K(305856K)] 329644K->72932K(1004928K), 0.0688340 secs] [Times: user=0.42 sys=0.01, real=0.07 secs]
19.372: [GC [PSYoungGen: 273171K->43621K(305856K)] 302483K->76957K(1004928K), 0.0573890 secs] [Times: user=0.41 sys=0.01, real=0.06 secs]
19.430: [Full GC (System) [PSYoungGen: 43621K->0K(305856K)] [ParOldGen: 33336K->54668K(699072K)] 76957K->54668K(1004928K) [PSPermGen: 36356K->36296K(204800K)], 0.4569500 secs] [Times: user=1.77 sys=0.02, real=0.46 secs]
19.924: [GC [PSYoungGen: 4280K->128K(305856K)] 58949K->54796K(1004928K), 0.0041070 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
19.928: [Full GC (System) [PSYoungGen: 128K->0K(305856K)] [ParOldGen: 54668K->54532K(699072K)] 54796K->54532K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.3531480 secs] [Times: user=1.19 sys=0.10, real=0.35 secs]
20.284: [GC [PSYoungGen: 4280K->64K(305856K)] 58813K->54596K(1004928K), 0.0040580 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
20.288: [Full GC (System) [PSYoungGen: 64K->0K(305856K)] [ParOldGen: 54532K->54532K(699072K)] 54596K->54532K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2360580 secs] [Times: user=1.01 sys=0.01, real=0.24 secs]
20.525: [GC [PSYoungGen: 4280K->96K(305856K)] 58813K->54628K(1004928K), 0.0030960 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
20.528: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54532K->54533K(699072K)] 54628K->54533K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2311320 secs] [Times: user=0.88 sys=0.00, real=0.23 secs]
20.760: [GC [PSYoungGen: 4280K->96K(305856K)] 58814K->54629K(1004928K), 0.0034940 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
20.764: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54533K->54533K(699072K)] 54629K->54533K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2381600 secs] [Times: user=0.85 sys=0.01, real=0.24 secs]
21.201: [GC [PSYoungGen: 5160K->354K(305856K)] 59694K->54888K(1004928K), 0.0019950 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
21.204: [Full GC (System) [PSYoungGen: 354K->0K(305856K)] [ParOldGen: 54533K->54792K(699072K)] 54888K->54792K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2358570 secs] [Times: user=0.98 sys=0.01, real=0.24 secs]
21.442: [GC [PSYoungGen: 4280K->64K(305856K)] 59073K->54856K(1004928K), 0.0022190 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
21.444: [Full GC (System) [PSYoungGen: 64K->0K(305856K)] [ParOldGen: 54792K->54792K(699072K)] 54856K->54792K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2475970 secs] [Times: user=0.95 sys=0.00, real=0.24 secs]
21.773: [GC [PSYoungGen: 11200K->741K(305856K)] 65993K->55534K(1004928K), 0.0030230 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
21.776: [Full GC (System) [PSYoungGen: 741K->0K(305856K)] [ParOldGen: 54792K->54376K(699072K)] 55534K->54376K(1004928K) [PSPermGen: 36538K->36537K(204800K)], 0.2550630 secs] [Times: user=1.05 sys=0.00, real=0.25 secs]
22.033: [GC [PSYoungGen: 4280K->96K(305856K)] 58657K->54472K(1004928K), 0.0032130 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
22.036: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54376K->54376K(699072K)] 54472K->54376K(1004928K) [PSPermGen: 36537K->36537K(204800K)], 0.2507170 secs] [Times: user=1.01 sys=0.01, real=0.25 secs]
22.289: [GC [PSYoungGen: 4280K->96K(305856K)] 58657K->54472K(1004928K), 0.0038060 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
22.293: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54376K->54376K(699072K)] 54472K->54376K(1004928K) [PSPermGen: 36537K->36537K(204800K)], 0.2640250 secs] [Times: user=1.07 sys=0.02, real=0.27 secs]
22.560: [GC [PSYoungGen: 4280K->128K(305856K)] 58657K->54504K(1004928K), 0.0036890 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
22.564: [Full GC (System) [PSYoungGen: 128K->0K(305856K)] [ParOldGen: 54376K->54377K(699072K)] 54504K->54377K(1004928K) [PSPermGen: 36537K->36536K(204800K)], 0.2585560 secs] [Times: user=1.08 sys=0.01, real=0.25 secs]
22.823: [GC [PSYoungGen: 4533K->96K(305856K)] 58910K->54473K(1004928K), 0.0020840 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
22.825: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54377K->54377K(699072K)] 54473K->54377K(1004928K) [PSPermGen: 36536K->36536K(204800K)], 0.2505380 secs] [Times: user=0.99 sys=0.01, real=0.25 secs]
23.077: [GC [PSYoungGen: 4530K->32K(305856K)] 58908K->54409K(1004928K), 0.0016220 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
23.079: [Full GC (System) [PSYoungGen: 32K->0K(305856K)] [ParOldGen: 54377K->54378K(699072K)] 54409K->54378K(1004928K) [PSPermGen: 36536K->36536K(204800K)], 0.2320970 secs] [Times: user=0.95 sys=0.00, real=0.23 secs]
24.424: [GC [PSYoungGen: 87133K->800K(305856K)] 141512K->55179K(1004928K), 0.0038230 secs] [Times: user=0.01 sys=0.01, real=0.01 secs]
24.428: [Full GC (System) [PSYoungGen: 800K->0K(305856K)] [ParOldGen: 54378K->54950K(699072K)] 55179K->54950K(1004928K) [PSPermGen: 37714K->37712K(204800K)], 0.4105190 secs] [Times: user=1.25 sys=0.17, real=0.41 secs]
24.866: [GC [PSYoungGen: 4280K->256K(305856K)] 59231K->55206K(1004928K), 0.0041370 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
24.870: [Full GC (System) [PSYoungGen: 256K->0K(305856K)] [ParOldGen: 54950K->54789K(699072K)] 55206K->54789K(1004928K) [PSPermGen: 37720K->37719K(204800K)], 0.4160520 secs] [Times: user=1.12 sys=0.19, real=0.42 secs]
29.041: [GC [PSYoungGen: 262208K->12901K(275136K)] 316997K->67691K(974208K), 0.0170890 secs] [Times: user=0.11 sys=0.00, real=0.02 secs]
Edited by: 807460 on Feb 6, 2011 8:28 PM

What do you see if you use the least number of options you need to start the application. I would try just
-mx1024M -XX:MaxPermSize=512M I would only add options which appear to improve performance.

Field "Reason for change" mindatroy in PO under "Version" tabe ?

Hello Exp.,
Is there any EXIT or BADI available to make "Reason for change" mandatory while changing PO in ME22N tcode.
In SPRO, is there any standard location where we can make this field mandatory? .
Input and suggestion is highly appreciable.
Regards
Sanjay

Dear sir,
go to SPRO-IMG-Materials Management-Purchasing-Version Management-Set Up Version Management for External Purchasing Documents.
select your document type for which you want to make the required entry reason for change. and click details indicator(CtrlshiftF2). and in field selection Reason field make the Required entry.
then when u r changing PO the system will ask required entry for reason for change.
regards
jrp

WLK1 Table mandatory field data for DATBI & DATAB missing

Hi ABAPers,
I have an issue in production i.e in table WLK1 few records have created which have data missing from mandatory field DATBI & DATAB . Can anyone tell me the reason for that and how to delete those records.
Thanks,
Soumya .

Here in our case we are creating materials and availing certain time period i.e. DATAB and DATBI for selling those in different stores. So if those goes missing will certainly cause problem.
So, just by a creating Z code for selcting those records then deleating them and after that listing them again to database will solve the problem or not?
Thanks.

Mandatory field "Priority" for maintenance plan

Hi,
Setting mandatory fields on preventive maintenance plan is not possible in customizing.
So the alternative are:
     - User-exit as described above (TCode SMOD)
     - Transaction variants (TCode SHD0)
I've tried SMOD: this approach is not a user friendly option. The user get an error but the field are greyed out and need to click on cancel before the are able to enter data.
So I triend the screen variant (SHD0). But I'm having an issue on the field "Priority" (RMIPM-PRIOK). The dropdownlist is not working...
Does anyone has a workaround? I want to avoid development...
Thanks,
Laura

Hi Laura,
I understand that you are trying to make the Priority field (PRIOK) in maintenance item mandatory. It is a very simple task with User-Exit. Just put the following code in the include ZXPRMU06 of user-exit IPRM0004.
IF IMPOS_IMP-PRIOK IS INITIAL.
   MESSAGE: 'Please Fill the Priority field.' TYPE 'I'.
   RAISE NO_UPDATE.
ENDIF.
You will get this message and the Plan is refused to be saved until Priority Field is filled.
Your ABAPer will be able to do it in few seconds.
Jogeswara Rao K
PS: Also for me SHD0 option has always been last resort.

How to skip the mandatory field validation for clearing the screen fields

Hi Friends,
I have created a module pool screen, and made some fields mandatory. after entering some fields, if i try to clear the fields, am unable to clear. Its throwing the error "Enter all required fields"., since some mandatory fields are there. But i could able to navigate through other screen. Both the "CLEAR" and "NEXT" command are given in the at-exit command only. Next is working but clear is not working.
Please provide me the solution.
Thanks
Karthikeyan.L

Hi,
To avoid automatic input checks you have to assing function type - E to appropriate screen field, which is not to be checked.
These function codes don't trigger PAI processing, instead they go directly to
MODULE mod AT EXIT-COMMAND.
..placed in PAI of the screen. In this way you can ommit automatic checks performed by system on mandatory fields. Please ensure you have assing E type to next and clear functions in GUI status.
Regards
Marcin

Reason for delay on the DS planning board grafic

Dear SAP Fans
Have you done any development on the DS planning board to show reason of the delay of a planned order?
We are implementing PP/DS and this is a hard requirement for the acceptance. The users have another schedule system with this functionality, when an order is delayed you can see the reason in the chart by clicking on the delayed order. When they see the reason they can see all the constraints that prevent the optimizer to schedule the planned order in an early date, for example:
- Order 0001 is delayed to 15.04.2011 because;
         - Reason 1: Machine A is unavailable up to 30.03.2011
         - Reason 2 : Componente 0001-01 have purchase order scheduled to 15.04.2011
         - Reason 3 : PRT is under maintenance up to 10.04.2011
With this information on hand the user can take some actions to antecipate the order in case this order is causing delay on a priority A customer order. For example the actions could be:
          - For reason 1, rearrange orders in the machine to schedule the order in an early date.
          - For reason 2, negotiate with supplier an early delivery date.
          - For reason 3, negotiate with plant maintenance to accelerate it.
Maybe something related to look for the delay log of a specific order.
Appreciate any insight.
Thanks and BR

hello,
first check the operations of the order.
right click on the produce operation and navigate to Order Processing.
In the order tree open all nodes for operations.
Is the set up activity visible there?
If yes doble click on the activity.
does the set up activity have a duration?
If yes check the status of the set up activity.
go back to the planning board.
in the menue select extras-> Legend
a pop-up with the graphical objects is displayed.
Check the graphic objects for the activity status you read before.
did you change the customizing settings for the graphic object?
If yes check them again or reset them to the default SAP settings.
I had a similar problem with a set up activity when I wanted to change the color of the activity according to the set up group. I changed the settings in the customizing Maintain Planning Board Profiles.
It is very difficult to maintain the decision table for graphical objects.
If you did this recheck the decision table.
Go back to the SAP default settings and check the planning board again.
Are the set up acitvities displayed now?
Then the porblem is with the decision table.
rethink every step again.

What is the reason for stock/requirements list disabled in MM03

Hi,
I hv a problem where display a material in MM03, the stock/requirements list is disable. When run in MD04, error date comes after end of valid factory calendar. (Please correct)
I hv corrected the PO delivery date but still the same, wht shld I check now ?
Thanks in advance for anyone reply my question.

extend your factory calendar using transaction SCAL
What you described has probably to do with some field values entered in the material master like delivery days, planning time fence ....
which make the planning determine a date for that you dont have a factory calendar.

WTY2 (labor value catalog, field Key for item type Labor Value)tcode J3GK01

Hi
We wrongly create data in WTY2 (tcode J3GK01), now we want to delete/inactive the data, how we want to delete/inactive the data. Can i just change at se16n and change the Deletion ind = Yes. Does it have any impact if i just change like this..
tq

Hi,
Just check if this method is useful:
In T Code J3GK02
Enter Catalog = WTY2
No.in Catalog = <the value to be deleted>
Press Enter and go to "Change Number in Catalog: Detail Screen"
Go to Edit --> Deletion Flag --> Set
The Field Deletion Ind. gets automatically set to 'Yes'
Save the transaction.
When you use this Catalog Number in the WTY screen, system displays the following message:
"No catalog entry found for catalog number"
Raj

Accept / Rejection Reasons for Shopping Cart Approval

Hi experts!
Our customer would like to have the following functionality.
During approval workflow the user will either Accept or Reject the shopping cart and at the same time he must enter a reason for approval / rejection from a list with fixed texts / values.
I didn't find any documentation about rejection reasons during approval of shopping cart. Has anybody of you ever seen this or realized anything like that?
If SAP Standard doesn't offer anything suitable we might have to modify the approver screen or develop a new screen.
Any helpful answer would be much appreciated.
Best regards,
Corinne

Hi
<b>Please try this -></b>
Re: Make mandatory field-Reason for rejection notes-SC approval screen
Reason for Return Delivery missing
Re: Text Types Issue on Bid/Quote
Temporary GUID coming from Sourcing in Doc change badi
Reason for Return Delivery
inactive approval and reject buttons on shopping cart approval screen
<u>Else Use BBP_DOC_CHECK_BADI</u>
SC header level Reject- Display error message
Hope this will help. Do let me know.
Regards
- Atul

QA32 or QA11 - reason for movement field enable to QA32 ,inspection screen

Hi friends,
while doing goods receipt MIGO 101 quality stock. material document posted.
i added field(Reason for movement ) for 101 mov type.
When i want try at QA32 for quality to blocked stock i need to enter reason for blocked stock like pending or waiting for approval.
here system not appeare reason for movement field in QA32 screen.
how to enable reason for movement at QA32 inspection stock screen.
Edited by: sivasankar cherukuri on Jul 7, 2010 11:53 AM

Issue closed. my self

Reg: "Reason for ordering" field in Scheduling Agreement.

Hi guys,
I am not getting the field "Reason for Ordering" in Scheduling Agreement.(ECC 6.0).
I am getting the same field in PO in "Retail" tab.
Any body can help me in this aspect.
Kannan

Hi,
This field is not available for Scheduling Agreement. It is only available for Purchase Order.
Even you will not get this in Field selection also.

Mandatory field 'Reason for Delay" required in VKM3 Tcode application

Similar Messages

Maybe you are looking for