Help regarding Scheduling date calculation in APO using Condition Technique

Hi Team,
The below is the issue I am facing. Could you please help me regarding this?
For a material MAT1, a stock of 15 is available today i.e. on 15/05/2014 and a Planned Order of 35 is available on 01/08/2014. I have created a Sales Order of 50 today i.e. 15/05/2014 for this material with a RDD of 20/05/2014. I have maintained the LEAD and the TRAN times as 5 days and 10 days respectively. These are maintained for a particular Route. LOAD, PICK, and UNLD are 0. In the Location master, I haven't defined any Calendar. So, it has to consider all days as working without any holidays.
For the given RDD of 20/05/2014, system performs the backward scheduling and arrives at a past date of 05/05/2014(20/05/2014-5D-10D) for the MBDAT. Since this date is in the past, the system should set the MBDAT to the current system date i.e. 15/05/2014. Since PICK is 0, the Loading Date also should be 15/05/2014. Since LOAD is 0, the Goods Issue Date also should be 15/05/2014. Since LEAD and TRAN are 5D and 10D, the Delivery Date should be 15/05/2014+5D+10D=30/05/2014.
But, in the Sales Order, I am getting a different date. For MBDAT, Loading Date, and Goods Issue date, the dates are 05/07/2014. Transportation Planning Date is 25/06/2014 and Delivery Date is 01.08.2014. During the GATP check, I am getting only a partial confirmation of 15 and the planned order of 35 is not being considered.
The material is APO relevant and the Scheduling using Condition Technique is being used.
Kindly help me regarding this and let me know if I am missing anything here.
Thanks in advance for the help.
Thanks & Regards,
Srikanth.

Hello Srikanth,
Let us differentiate the problem into two pieces.
1) Incorrect Scheduling
2) Future receipts not being considered.
For the second problem, future reciepts not being considered, which is on 01/08/2014, please check if your system is allowing you to go further and do the confirmation. How long is your Checking Horizon ? Is your checking horizon configured enough to go ahead and pick this reciept element to give the confirmation by creating a second schedule line ?
For the first problem, LEAD to the best of my knowledge is transportation planning time which means, the MBDAT would be shifted to the extent of the LEAD time to be able to manage the truck though the stock is available today. However, the dates mentioned by you seems to be completely different. Hence, I suggest you to take the ATP check on this line item, go to Delivery proposal screen and click on the graphical representation of the Scheduling results. There you should be able to understand how the calculation is actually happening. Perhaps, there are some calendars that are being used which you'd not be knowing ? May be the condition record has different times maintained in the condition table ? Check the condition table that the system is picking up ? May be you have maintained the route and transportation scheduling in "X" condition table, however system was able to identify a different detailed level table which satisfied the condition and due to which system got the scheduling calculated accordingly ?
May be it is a good idea to investigate this way. Hope this helps.
Babu Kilari

Similar Messages

Transportation time using condition technique!!

Hi All,
Can anyone tell how transportation time is calculated using condition technique (APO)? we have defined following in access sequence for scheduling
Plant
Destination country
Spd trans. zone
Shipping Conditions
Weight group
Factory Calendar ID
Now if no transportation lane is defined between plant A and ship to party B. Then how system is going to calculate the delivery date? where do we define transportation time between A and B or how it is getting calculated?

HI,
You can define a specific transporation duration in the condition technique per chracteristic (e.g. Shipto, plant, etc.).
Create new condtion records via TA /sapCND/AU11. Create a entry for TRAN and choose a access sequence. There you define a duration e.g. for a ship-to, etc.
Three options to find a transporation duration:
1. Directly from the transportation lane (TA /SAPAPO/SCC_TL1)
2. Estimated by the system if the transporation lane does not contain any duration (except if the Fix-Duration Indicator was set, note 1464309)
(The system calculates the transportation time based on the distance between the start and destination location and the average speed of the means of transport used.)
3. from the contion technique (TA /SAPCND/AU11)
(A Transportation calendar can be defined just via scheduling userexit 002 for the condition technique.)
Further details in the SAP Help Docu:
http://help.sap.com/saphelp_scm50/helpdata/en/3a/92e217b3f54a5eae7a4ac8a99e5e87/content.htm
Hope it helps.
regards,
Michael
Edited by: Michael Thinschmidt on Aug 31, 2010 3:41 PM

Functions which uses condition technique in SD

Hai Guys,
   Do help me out in getting informations about the
   following.
pls tell the functions which uses condition technique in SD
detailed answers or links for this pls...
Thanku
Regards
Jino

Hi Jino,
ntroduction to the Condition Technique Locate the document in its
Use
This section describes the elements within the condition technique. It is organized to reflect the likely sequence of events that you go through when you implement pricing in Customizing. The standard R/3 System includes predefined elements for routine pricing activities. For example, the standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. In the case of each element, you can use the standard version, modify the standard version, or create entirely new definitions to suit your own business needs. The sequence of activities is generally as follows:
   1. Define condition types for each of the price elements (prices, discounts, and surcharges) that occur in your daily business transactions.
   2. Define the condition tables that enable you to store and retrieve condition records for each of the different condition types.
   3. Define the access sequences that enable the system to find valid condition records.
   4. Group condition types and establish their sequence in pricing procedures.
For more information about implementing and customizing pricing in sales order processing, see Customizing for Sales and Distribution.
For a more technical description of how the condition technique works, see the Business Workflow documentation for Message Control.
Elements Used in the Condition Technique
Condition Types
Condition Tables
Access Sequences
Pricing procedures
Condition Types Locate the document in its SAP Library structure
Use
A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.
Example
Example of a Condition Type
You define the condition type for a special material discount. You specify that the system calculates the discount as an amount (for example, a discount of USD 1 per sales unit). Alternatively, you can specify that the system calculates the discount as a percentage (for example: a 2% discount for orders over 1,000 units). If you want to use both possibilities, you must define two separate condition types. The following figure illustrates how condition types can be used during pricing in a sales document.
This graphic is explained in the accompanying text
In the example in the preceding figure, two discounts apply to the item in the sales order. The first discount is a percentage discount based on the quantity ordered. The second discount is a fixed discount based on the total weight of the item.
Note
You determine the calculation type for a condition type in Customizing. This determines how the system calculates prices, discounts and surcharges for a condition. When setting up condition records, you can enter a different calculation type than the one in Customizing. At present all available calculation types are permitted. The field Calculation type can however not be accessed if this field is left empty. After the data release has been printed, if the field has not been completed manually, the proposal is automatically taken from Customizing. After this it is no longer possible to make manual changes.
If you use different calculation types for what are otherwise the same conditions (for example, percentage, as a fixed amount or quantity-dependent), you do not have to define different condition types in Customizing. You can set a different calculation type when maintaining the individual condition records.
Condition Types in the Standard R/3 System
The standard system includes, among many others, the following predefined condition types:
Condition type
Description
PR00
Price
K004
Material discount
K005
Customer-specific material discount
K007
Customer discount
K020
Price group discount
KF00
Freight surcharge (by item)
UTX1
State tax
UTX2
County tax
UTX3
City tax
Creating and Maintaining Condition Types
You can change and maintain condition types provided in the standard version of the SAP R/3 System or you can create new condition types to suit the needs of your own organization. You create and maintain condition types in Customizing.
To reach the condition type screen from the initial Customizing screen for Sales and Distribution:
   1. Basic Functions
      ® Pricing ® Pricing Control ® Define condition types.
      A dialog-box appears, listing the transaction options. Select the corresponding transaction for defining the condition types.
   2. In the Conditions: Condition Types view, you can change existing condition types or create new ones.
Leaving content frame
Condition Tables Locate the document in its SAP Library structure
Use
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
Example
Example of a Condition Table
A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:
Sales organization
Distribution channel
Customer
Material
The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record.
The following figure illustrates the connection between the condition table and the subsequent condition records.
This graphic is explained in the accompanying text
Condition Tables in the Standard Version
The standard system includes predefined condition tables and specifies them for each access in each predefined access sequence.
Creating or Maintaining Condition Tables
You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.
From the initial screen of Customizing for Sales and Distribution, you reach the condition table screens by choosing Basic functions ® Pricing ® Pricing Control ® Define condition tables. Then select the mode you want to work with (create, change, display).
Information About Fields
The fields that you choose to make up the key are called the selected fields. The fields from which you can make your selection are called the allowed fields.
Selected Fields
The preceding figure shows the fields that make up the key for condition table 005 (the table for customer/material condition records in Sales). The selected fields show organizational data, such as Sales organization.The fields Customer and Material define the relationship between a particular customer and material.
Field Catalog (Allowed Fields)
When you select fields for the key, you must choose the fields from the list of allowed fields.
Making Changes to Condition Tables
You can make limited changes to existing condition tables. For example, you can change the name of the table or the format of the fast entry screens for the condition records. (Fast entry screens are screens where you can quickly, on a single screen, create and maintain the condition records that refer to the condition table).
Format of a Fast-Entry Screen
The screen consists of header and item lines. Each item line represents a separate condition record. The header lines include the fields that are general to all item lines. When deciding on the format of the fast-entry screen, you can determine whether each field in the key appears as a line in the header or as an item line.
Changing the Format of a Fast-Entry Screen
To change the format of the Fast-Entry screen, choose F6 (Technical View) on the screen where you create or maintain a condition table.
When you determine the format, you have the following possibilities:
If you want the...
Do the following...
Field to appear as a header line
Leave the line field blank
Field to appear as an item
Mark the line field
Text for an item line to appear
Mark the text field
After you make changes to a condition table, choose F16 Generate) to regenerate the table.
Creating a New Condition Table
You can create new condition tables to meet the pricing needs of your organization. When you create a new condition table, you select a combination of fields from the list of allowed fields. The selected fields define the key for the subsequent condition records.
Before you select the fields for the key, there are two things to consider:
The sequence (or hierarchy) of the fields
Which fields you want to appear in the header and item areas of the corresponding fast-entry screens
Important Fields
In sales, the fields you should take into consideration are Sales organization and Distribution channel. The sales organization is nearly always used as a criteria in pricing, because different sales organizations often want to use their own prices, discounts, and surcharges. If you use the sales organization as a criterion in pricing, you should also use the distribution channel. If you do not want to establish different prices, discounts, and surcharges for each distribution channel, use the field anyway. In Customizing for Sales, you can use one distribution channel as a reference for all others (thereby sharing the same pricing data).
Deciding the Sequence of Fields
The order of the fields in a condition table affects the performance of the system during pricing. Two general guidelines will help you create an efficient condition table:
   1. If you select fields that are connected to the structure of your organization (for example, sales organization and distribution channel), assign the fields according to the level of general applicability: Put the most general field, for example, the sales organization in the highest position and the most specific field in the lowest.
   2. After organizational fields, place fields from the document header before those that come from the item level. (For example, Customer comes before Material)
After you have selected the fields for the key on the screen where you maintain and define condition tables, choose F16 Generate to generate the table in the system. Generation prepares the condition table for storing condition data.
Access Sequences Locate the document in its SAP Library structure
Use
An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record. You specify an access sequence for each condition type for which you create condition records.
Note
There are some condition types for which you do not create condition records (header discounts that you can only enter manually, for example). These condition types do not require an access sequence.
ExampleA sales department may offer customers different kinds of prices. The department may create, for example, the following condition records in the system:
A basic price for a material
A special customer-specific price for the same material
A price list for major customers
During sales order processing, a customer may, in theory, qualify for all three prices. The access sequence enables the system to access the data records in a particular sequence until it finds a valid price. In this example, the sales department may want to use the most favourable price for a certain customer. For this reason, it ensures that the system searches for a customer-specific price. The following figure shows how the system searches for the relevant record.
This graphic is explained in the accompanying text
Access Sequences in the Standard R/3 System
The standard R/3 System contains access sequences that are predefined for each of the standard condition types. The names of the access sequences often correspond to the condition types for which they were designed. For example, the access sequence for a material discount (condition type K004) is also called K004.
Creating and Maintaining Access Sequences
You create and maintain access sequences in Customizing. For more information, see the online Implementation Guide for Sales and Distribution.
To reach the access sequence screen, go to the initial screen for Sales and Distribution Customizing and choose:
   1. Basic Functions
      ® Pricing ® Pricing Control ® Define access sequences
Select the transaction that you want to execute (Maintain access).
Leaving content frame
Pricing Procedures Locate the document in its SAP Library structure
Use
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
   1. Choose Basic Functions
   2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.
Thanks&Regards,
Phani,
Points If helpful.

How to determine the process alias using condition technique in Transportation & Shipment Scheudling?

Dear All,
I am trying to use the functionality Transportation and Shipment Scheduling in GATP.
I would like to know that how the sytem determines the process alias using condition technique in Transportation & Shipment Scheudling?
As the Transportation & Shipment Scheduling functionality can be extended further by using the configurable process to overcome the complex scenario. But it needs that process alias should not be determined by using the condition technique.
Moreover, is it possible to use both functionality simultaneously in the system. i.e. Transportation and Shipment Scheduling using condition technique and Transportation and Shipment Scheduling using configurable process?
Thanks & Regards
Piyush Ranpura

Hi Piyush,
I have added a small overview in the SCN WIKI which shows you the two ways for the process alias determination and also here as attachment:
http://wiki.sdn.sap.com/wiki/display/SCM/Time+and+Scheduling+Functions
Yes, depending on your customizing you can use both scheduling methods in parallel. e.g. you activate CPS just for a specific ITEM category or product and/or customer and/or....what ever you want.
best regards,
Michael

Schedule Dates changed by APO

Hi APO people
I have a problem in PP whereby the production order schedule dates are immediately overridden by the APO CIF. As a result no scheduling can be done. We are not using PP/DS for scheduling but a third party system. We have also tried using the Capacity Planning table in R/3 but the result is the same.
Is there some setting in APO which prevents this form happening.
In addition to this even trying to change basic dates manually is not possible. Occasionally if a re-read of PP master data is done on the order, dates are allowed to change but this appears to be inconsistent as sometimes it works and other times it doesnt.
Thanks for the help!

If the qty is not transmitted to the vendor using message transmission, system does not firm the qty with in planning time fence.
So pls chk your planning time fence as well.
Also pls chk the below link
http://help.sap.com/saphelp_46c/helpdata/en/f4/7d2a5b44af11d182b40000e829fbfe/content.htm
BR,
Krishna

Schedule date calculation

Hi All,
While creating production order, in scheduling date is not calculating correctly.
In routing for define work center, number of individual capacities is 10.
Working time is 8 Hrs, therefore total capacity is 80 Hrs
In routing for base qty 1 number machine time is given 8 hrs.
There is no weekly off.
Now when i am creating order for 10 numbers base of above details system giving date of next 10 days.
But as per my avaiable capacity it should give schdule date of today only (same day).
I have check same data by increasing capacities and i found by increasing any number of individual capacities system schedule date is not changing.
Plz tell me what shoud problem, is there any master data error or configuration?
Regards
Rajesh

hi,
In the Routing for the material . IN THE OPERATION OVERVIEW - SELECT THE OPERATION IN WHIICH YOU USE THE WORK CENTER WITH 10 CAPACITY - MAINTIANED the tick mark against 'split ' and give the number no 'split'(IN YOUR CASE 10)
so system use how many split that you given in the routing .

Regarding scheduling dates & time

Hi,
1)i have created a production order for a finish material "A" mentioning finish dates 21/05/08.
2)order qty is 100 kg's time taken is 1 hour( i.e. 24:00 to 23:00).
NOW,
3) when i create the production order for the same material "A" again, for the qty 200 kg's & finish date is 21/05/08.
4) finish time is taking from 24:00 instead of 23:00.
Actually it should start from 23:00 right????
i think i missed out some settings.
i need all of your suggestions for the above problem.
thanks/regards
vish

Hi ,
Scheduling depends on the option you select on MD02 screen , if you have selected Determine basic dates then it will search In house production time mentioned in material master . If you select 2 nd option i.e lead time scheduling and capacity planning then system will refer routing ( cap requirements will also be created ).
R/3 does not consider capacity while scheduling the order so check either in house production time or from routing check scheduling results for 100 or 200 quantity .
Reward if useful .
Neal .

Delivery Scheduling Date Calculation

When I am creating Deliveries using VL10B for the Stock Transport Order, the loading date, shipping date, picking date etc, are all same as delivery date. I want the system to create deliveries at least 4 days in adavance and start preparing.
What needs to be done.
Where can I create this time floats for separate tasks to finish i.e. Delivery scheduling.

no solution.

Need help regarding Simple Data Client and Simple Data Server VIs

Hi everyone.
I have a simple objective. I just want to test the 2 example VIs, "Simple Data Client" and "Simple Data Server" between 2 computers. I just want to check whether is this working between the 2 computers.
What I have done for now is that I changed the "address", from "localhost" in the "Simple Data Client.vi" to the IP address of the computer running the "Simple Data Server". I runned the "Simple Data Server" VI in one of the computers first followed by the "Simple Data Client" in the other computer. Nothing is received and the client just timed out.
Can anyone please help me troubleshoot and tell me what are the possible problems for this? Are there any wires connections between 2 computers that I am missing or any other configurations I have to make before I can successfully do this?
Thanks.
Regards,
Jonathan

Hi Lee.P.
I understand that. I was just feeling frustrated about the project not working. Sincere apologies from me.
I was wrong about the error number. It is not Error 60. It is Error 59 - The network is down, unreachable, or has been reset.. Yes, I have tried changing the port numbers at the 2 computers when trying to send/receive.
Could anything else be the problem?
Regards,
Jonathan

Need some help regarding value date

hiii experts...i want little clarification about value date and its effects... i searched scn and google but my issue is like...when we receive cheque today i.e 11/06/2014... it will be come in bank a/cs nearly on 14/06/2014... so if we write the value date 14/06/2014... will that bank ledger show effect on 14/06/2014... moreoveer the user posted a entry development server for 1/3/2014 and gave value date of 1/4/2014.. now in faglb03... how it will reflect..i know its basic question but i didnt find any solution through searching soo posted... please guide me..
Regards
Abhay

hey mani... thankss for the reply... its shows the meaning which i understood but the effect in ledger... when it will show... value date or posting date??
e.g
a customer gives cheque today 11/6/2014.. user deposits cheque today and it will come into bank account near on 14/6.2014..
IN SAP
user does entry today i.e 11/06/2014
in bank g/l... he gives value date 14/06/2014... now when he posts the entry... the entry will shown in ledger on 11/06/2014... but the actual amount will come in 14/06/2014... soo my question is ... whts the user of value date then if he is posting the document on posting date

Formula variable using date char - unable to use conditions

Hello Experts,
I am sure I am making a silly mistake here - but after spending lot of time I am unable to rectify this - please help if you can:
I basically want the report to show only latest employee actions for a selected period (usually month).
1. I am using formula variable that is based on 0CALDAY and defined as number.
2. A calculated keyfigure uses this formula variable. Both calculated keyfigure and CALDAY char are included in the report / navigation.
3. There is a condition defined using calculated keyfigure. No matter what logic I use, I just cannot use calculated keyfigure to filter records on the report. My original idea was to use Top N - 1 with char combination as 'Employee' to get me the latest employee records for each employee.
Can anyone help spot where I am going wrong?
Thanks.

I haven't looked at that, but as a first guess idea- why not use the picker to get a date, then save it as a number of seconds from a given date?
See:
dateWithTimeIntervalSince1970:
Creates and returns an NSDate object set to the given number of seconds from the first instant of 1 January 1970, GMT.
+ (id)dateWithTimeIntervalSince1970:(NSTimeInterval)seconds
Or you could store it as a string, but I think the number would be easier.

Schedule Lines in APO using CTM

Dear Experts,
How to create schedule lines directly in APO using CTM?
Thanks adn regards,
Sushant

Hi,
Do you mean creation of Planned orders by CTM against the demand /
Generally "schedule lines" term in APO are seen in RRP3 Product view and refers to Planned order / purchase requisitions.
Yes CTM can create schedule lines in APO after CTM planning run.
Thanks,
Pavan Verma

Can vlan.dat file be collected using SCP on LMS 4.2 ?

Hello, I need help regarding vlan.dat file fetch.
I'm using Cisco Prime 4.2 and VLAN fetch for all devices is currently going over TFTP. Devices managed by LMS are 2960, 4500, 6500 series. All devices are using SSH v2. ACS server is configured on all devices and SSH credentials are OK.
This is the error meessage I get when i select SCP: "SCP user credentials not available. Configure the SCP user credentials and try again Action: Check if protocol is supported by device and required device package is installed."
Is it possible to use SCP as VLAN fetch protocol? How to configure this on a devices and how to enter SCP credentials in LMS?
Thanks.

I don't think anything other than tftp is supported as the transport protocol for actual transfer of the vlan.dat file from the switches by LMS.
See this post where Joe C. describes how LMS logs into the target device (via telnet or ssh) and then transfers the files back to itself using tftp. That's about 2-1/2 years old but matches what's described in the current LMS Configuration Management user guide, quoted here:
"VLAN — Count of the successful VLAN configuration fetches for each protocol. This configuration fetch is supported by only Telnet and SSH protocols."
You also have the option (as of LMS 4.2) of turning off vlan.dat collection since it is often of limited utility. Please refer to this thread for details.

Regarding parsing date

Hi,
I need to parse the following string:
String str ="08/23/2010 10:20 am" ;
as a date object i am getting the result as
Mon Aug 23 00:00:00 IST 2010
but i want to parse the string str as a date object in the same format i.e. "08/23/2010 10:20 am"
any help regarding this will be appreciated.
Thank You.

dvrsandeep wrote:
I need to parse the following string:
String str ="08/23/2010 10:20 am" ;
SimpleDateFormat can help you do this by parsing a String into a Date object.
as a date object i am getting the result as
*Mon Aug 23 00:00:00 IST 2010
This is not the "result" you're getting. If you are using SimpleDateFormat, you are getting a Date object which has no form. Perhaps this is the default toString returned from your Date object, but regardless, it's not the internal representation of the Date.
but i want to parse the string str as a date object in the same format i.e. "08/23/2010 10:20 am"
any help regarding this will be appreciated.Then use SimpleDateFormat again to format a Date object into a String.

Problem storing date in MS Access using JSP

Hi all,
Can anyone please help me storing date in MS Access using Java i am getting errors. I think it is probably because MS Access take "date/month". I am entering a string with date and month example
1st October as "0110". I don't know how to enter a date in MS Access.
Here is my code.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<%@page import="java.io.*"%>
<%@page import="java.sql.*"%>
<HTML>
<HEAD>
<TITLE> </TITLE>
</HEAD>
<BODY>
<%
   String emplno = request.getParameter("emplno");
   String date = request.getParameter("date");
   String proposal = request.getParameter("proposals");
   String network1 = request.getParameter("network");
   String suppassociates = request.getParameter("suppasso");
   String intmngt = request.getParameter("intmgt");
   String client[] = request.getParameterValues("client");
   String client1= request.getParameter("client1");
   String clientunit[] = request.getParameterValues("clientunit");
   String clientunit1=request.getParameter("clientunit1");
   int staffid = Integer.parseInt(emplno);
   double proposalunit=Double.parseDouble(proposal);
   double suppliersunit=Double.parseDouble(suppassociates);
   double networkunit=Double.parseDouble(network1);
   double internalmgtunit=Double.parseDouble(intmngt);
   Class.forName( "sun.jdbc.odbc.JdbcOdbcDriver" );
   Connection con = DriverManager.getConnection("jdbc:odbc:finalmp" );
   String activities= "INSERT INTO StaffActivities (StaffID,Date,ProposalUnit,NetworkingUnit,SuppliersAssociatesUnit,InternalMGTUnit) VALUES (?,?,?,?,?,?)";
   PreparedStatement pstmt = con.prepareStatement(activities);
   pstmt.setInt(1,staffid);
   pstmt.setString(2,date);
   pstmt.setDouble(3,proposalunit);
   pstmt.setDouble(4,suppliersunit);
   pstmt.setDouble(5,networkunit);
   pstmt.setDouble(6,internammgtunit);
   pstmt.executeUpdate();
   //String emplno="hello";
   //String entered_date="hello";
   //int access_date=0;
   //int user_date=0;
   if(pstmt!=null)
     pstmt.close();
   if(con!=null)
     con.close();
%>
</BODY>
</HTML>

i hope this can help you
public static String convertToISOFormat(Date dateTime) {
        // ISO Format: 'YYYY-MM-DD HH:MM:SS'
        String returnValue = fillLeft(String.valueOf(dateTime.getYear()+1900), 4,
                '0')
                + "-"
                + fillLeft(String.valueOf(dateTime.getMonth()+1), 2, '0')
                + "-"
                + fillLeft(String.valueOf(dateTime.getDate()), 2, '0')
                + " "
                + fillLeft(String.valueOf(dateTime.getHours()), 2, '0')
                + ":"
                + fillLeft(String.valueOf(dateTime.getMinutes()), 2, '0')
                + ":" + fillLeft(String.valueOf(dateTime.getSeconds()), 2, '0');
        return returnValue;
    }

Help regarding Scheduling date calculation in APO using Condition Technique

Similar Messages

Maybe you are looking for