BW 0CS_ORDER CLOSE DATE

Hi everyone,
Hope you are doing well.
I need help in the 0CS_ORDER infoObject (Service Order). In our solution, we call a service order as an engagement.
Currently, in the dashboards in our solution (like the Accounts Receivable Aging Report), all the engagements (open or closed) appear for a fiscal period/year. (Fiscal period/year is a variable in the selection screen.)
Now for the new change, the requirement is that an engagement should appear if it is open. And, if an engagement closes in a fiscal period/year, it should not appear in and after that fiscal period/year. That is, we need to consider the enagagement on the basis of its closed date or closed period/year.
I have included the "engagement closed period" as an attribute of the Engagement (0CS_ORDER) and loaded the master data for the new attribute.
Also, did the Attribute change run.
Then, made the "Eng closed period" as a NAV attribute in the multi-provider over which the AR Aging query is built.
The problem area for me is to write the condition (Closing period/year <= Fiscal period/year) at the query level.
We have a fiscal year characteristics variable in our query.
Please help me write the condition.
Looking for a quick response.
Thanks in advance!!!
Kriti

>
Amol Pawar wrote:
> Dear All,
>
> We use production orders and follow the normal process of WIP calculation and settlement for the same. But the users forgot to close some orders in the previous months and so they are showing in WIP. If we do TECO, the system considers TECO date as current date and the WIP will be reversed in current month settlement.
> I need to know how do I change the TECO date to previous periods so that I can reverse WIP in previous periods.
> Any help will be highly appreciated
>
> Regards,
> Amol
Amol,
There is no option to set TECO based on any date, system only can automatically set the date on which TECO was set. You can run settlement transaction with settlement period as last period but posting period should be current period(generally you are allowed to post in current period only).
Check with your FICO guy can may manual postings to correct the WIP for the periods.
Regards,
Prasobh

Similar Messages

Open data set and close data set

hi all,
i have some doubt in open/read/close data set
how to transfer data from internal table to sequential file, how we find sequential file.
thanks and regards
chaitanya

Hi Chaitanya,
Refer Sample Code:
constants:   c_split         TYPE c
                           VALUE cl_abap_char_utilities=>horizontal_tab,
           c_path          TYPE char100
                           VALUE '/local/data/interface/A28/DM/OUT'.
Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS : rb_pc    RADIOBUTTON GROUP r1 DEFAULT 'X'
                                USER-COMMAND ucomm,    "For Presentation
             p_f1     LIKE rlgrap-filename
                                      MODIF ID rb1,    "Input File
             rb_srv   RADIOBUTTON GROUP r1,             "For Application
             p_f2     LIKE rlgrap-filename
                                     MODIF ID rb2,     "Input File
             p_direct TYPE char128 MODIF ID abc DEFAULT c_path.
                                                       "File directory
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_f1.
*-- Browse Presentation Server
PERFORM f1000_browse_presentation_file.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_f2.
*-- Browse Application Server
PERFORM f1001_browse_appl_file.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF rb_pc = 'X' AND screen-group1 = 'RB2'.
      screen-input = '0'.
      MODIFY SCREEN.
    ELSEIF rb_srv = 'X' AND screen-group1 = 'RB1'.
      screen-input = '0'.
      MODIFY SCREEN.
    ENDIF.
    IF screen-group1 = 'ABC'.
      screen-input = '0'.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
*&      Form f1000_browse_presentation_file
      Pick up the filepath for the file in the presentation server
FORM f1000_browse_presentation_file .
CONSTANTS: lcl_path TYPE char20 VALUE 'C:'.
CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
      def_path         = lcl_path
      mask             = c_mask "',.,..'
      mode             = c_mode
      title            = text-006
    IMPORTING
      filename         = p_f1
    EXCEPTIONS
      inv_winsys       = 1
      no_batch         = 2
      selection_cancel = 3
      selection_error = 4
      OTHERS           = 5.
IF sy-subrc <> 0.
   MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    flg_pre = c_x.
ENDIF.
ENDFORM.                    " f1000_browse_presentation_file
*&      Form f1001_browse_appl_file
   Pick up the file path for the file in the application server
FORM f1001_browse_appl_file .
DATA: lcl_directory TYPE char128.
lcl_directory = p_direct.
CALL FUNCTION '/SAPDMC/LSM_F4_SERVER_FILE'
    EXPORTING
      directory        = lcl_directory
      filemask         = c_mask
    IMPORTING
      serverfile       = p_f2
    EXCEPTIONS
      canceled_by_user = 1
      OTHERS           = 2.
IF sy-subrc <> 0.
   MESSAGE e000(zmm) WITH text-039.
   flg_app = 'X'.
ENDIF.
ENDFORM.                    " f1001_browse_appl_file
*&      Form f1003_pre_file
    Upload the file from the presentation server
FORM f1003_pre_file .
DATA: lcl_filename TYPE string.
lcl_filename = p_f1.
IF p_f1 IS NOT INITIAL.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                = lcl_filename
        filetype                = 'ASC'
        has_field_separator     = 'X'
      TABLES
        data_tab                = i_input
      EXCEPTIONS
        file_open_error         = 1
        file_read_error         = 2
        no_batch                = 3
        gui_refuse_filetransfer = 4
        invalid_type            = 5
        no_authority            = 6
        unknown_error           = 7
        bad_data_format         = 8
        header_not_allowed      = 9
        separator_not_allowed   = 10
        header_too_long         = 11
        unknown_dp_error        = 12
        access_denied           = 13
        dp_out_of_memory        = 14
        disk_full               = 15
        dp_timeout              = 16
        OTHERS                  = 17.
    IF sy-subrc <> 0.
      MESSAGE s000 WITH text-031.
      EXIT.
    ENDIF.
ELSE.
   PERFORM populate_error_log USING space
                                    text-023.
ENDIF.
ENDFORM.                    " f1003_pre_file
*&      Form f1004_app_file
     upload the file from the application server
FORM f1004_app_file .
REFRESH: i_input.
OPEN DATASET p_f2 IN TEXT MODE ENCODING DEFAULT FOR INPUT.
IF sy-subrc EQ 0.
    DO.
      READ DATASET p_f2 INTO wa_input_rec.
      IF sy-subrc EQ 0.
*-- Split The CSV record into Work Area
        PERFORM f0025_record_split.
*-- Populate internal table.
        APPEND wa_input TO i_input.
        CLEAR wa_input.
        IF sy-subrc <> 0.
          MESSAGE s000 WITH text-030.
          EXIT.
        ENDIF.
      ELSE.
        EXIT.
      ENDIF.
    ENDDO.
ENDIF.
ENDFORM. " f1004_app_file
Move the assembly layer file into the work area
FORM f0025_record_split .
CLEAR wa_input.
SPLIT wa_input_rec AT c_split INTO
    wa_input-legacykey
    wa_input-bu_partner
    wa_input-anlage.
ENDFORM.                    " f0025_record_split
Reward points if this helps.
Manish

Exception Handling for OPEN DATA SET and CLOSE DATA SET

Hi ppl,
Can you please let me know what are the exceptions that can be handled for open, read, transfer and close data set ?
Many Thanks.

HI,
try this way....
DO.
    TRY.
    READ DATASET filename INTO datatab.
      CATCH cx_sy_conversion_codepage cx_sy_codepage_converter_init
            cx_sy_file_authority cx_sy_file_io cx_sy_file_open .
    ENDTRY.
READ DATASET filename INTO datatab.
End of changes CHRK941728
    IF sy-subrc NE 0.
      EXIT.
    ELSE.
      APPEND datatab.
    ENDIF.
ENDDO.

Download using open data set and close data set

can any body please send some sample pgm using open data set and close data set .the data should get downloaded in application server
very simple pgm needed

Hi Arun,
See the Sample code for BDC using OPEN DATASET.
report ZSDBDCP_PRICING no standard page heading
line-size 255.
include zbdcrecx1.
*--Internal Table To hold condition records data from flat file.
Data: begin of it_pricing occurs 0,
key(4),
f1(4),
f2(4),
f3(2),
f4(18),
f5(16),
end of it_pricing.
*--Internal Table To hold condition records header .
data : begin of it_header occurs 0,
key(4),
f1(4),
f2(4),
f3(2),
end of it_header.
*--Internal Table To hold condition records details .
data : begin of it_details occurs 0,
key(4),
f4(18),
f5(16),
end of it_details.
data : v_sno(2),
v_rows type i,
v_fname(40).
start-of-selection.
refresh : it_pricing,it_header,it_details.
clear : it_pricing,it_header,it_details.
CALL FUNCTION 'UPLOAD'
EXPORTING
FILENAME = 'C:\WINDOWS\Desktop\pricing.txt'
FILETYPE = 'DAT'
TABLES
DATA_TAB = it_pricing
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
GUI_REFUSE_FILETRANSFER = 6
OTHERS = 7.
WRITE : / 'Condition Records ', P_FNAME, ' on ', SY-DATUM.
OPEN DATASET P_FNAME FOR INPUT IN TEXT MODE.
if sy-subrc ne 0.
write : / 'File could not be uploaded.. Check file name.'.
stop.
endif.
CLEAR : it_pricing[], it_pricing.
DO.
READ DATASET P_FNAME INTO V_STR.
IF SY-SUBRC NE 0.
EXIT.
ENDIF.
write v_str.
translate v_str using '#/'.
SPLIT V_STR AT ',' INTO it_pricing-key
it_pricing-F1 it_pricing-F2 it_pricing-F3
it_pricing-F4 it_pricing-F5 .
APPEND it_pricing.
CLEAR it_pricing.
ENDDO.
IF it_pricing[] IS INITIAL.
WRITE : / 'No data found to upload'.
STOP.
ENDIF.
loop at it_pricing.
At new key.
read table it_pricing index sy-tabix.
move-corresponding it_pricing to it_header.
append it_header.
clear it_header.
endat.
move-corresponding it_pricing to it_details.
append it_details.
clear it_details.
endloop.
perform open_group.
v_rows = sy-srows - 8.
loop at it_header.
perform bdc_dynpro using 'SAPMV13A' '0100'.
perform bdc_field using 'BDC_CURSOR'
'RV13A-KSCHL'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RV13A-KSCHL'
it_header-f1.
perform bdc_dynpro using 'SAPMV13A' '1004'.
perform bdc_field using 'BDC_CURSOR'
'KONP-KBETR(01)'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KOMG-VKORG'
it_header-f2.
perform bdc_field using 'KOMG-VTWEG'
it_header-f3.
**Table Control
v_sno = 0.
loop at it_details where key eq it_header-key.
v_sno = v_sno + 1.
clear v_fname.
CONCATENATE 'KOMG-MATNR(' V_SNO ')' INTO V_FNAME.
perform bdc_field using v_fname
it_details-f4.
clear v_fname.
CONCATENATE 'KONP-KBETR(' V_SNO ')' INTO V_FNAME.
perform bdc_field using v_fname
it_details-f5.
if v_sno eq v_rows.
v_sno = 0.
perform bdc_dynpro using 'SAPMV13A' '1004'.
perform bdc_field using 'BDC_OKCODE'
'=P+'.
perform bdc_dynpro using 'SAPMV13A' '1004'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
endif.
endloop.
*--Save
perform bdc_dynpro using 'SAPMV13A' '1004'.
perform bdc_field using 'BDC_OKCODE'
'=SICH'.
perform bdc_transaction using 'VK11'.
endloop.
perform close_group.
Hope this resolves your query.
Reward all the helpful answers.
Regards

What is open data set and close data set

what is open data set and close data set,
how to use the files in sap directories ?

hi,
Open Dataset is used to read or write on to application server ... other than that i am not sure that there exists any way to do the same ... here is a short description for that
FILE HANDLING IN SAP
Introduction
Files on application server are sequential files.
Files on presentation server / workstation are local files.
A sequential file is also called a dataset.
Handling of Sequential file
Three steps are involved in sequential file handling
OPEN
PROCESS
CLOSE
Here processing of file can be READING a file or WRITING on to a file.
OPEN FILE
Before data can be processed, a file needs to be opened.
After processing file is closed.
Syntax:
OPEN DATASET <file name> FOR {OUTPUT/INPUT/APPENDING}
IN {TEXT/BINARY} MODE
This statement returns SY_SUBRC as 0 for successful opening of file or 8, if unsuccessful.
OUTPUT: Opens the file for writing. If the dataset already exists, this will place the cursor at the start of the dataset, the old contents get deleted at the end of the program or when the CLOSE DATASET is encountered.
INPUT: Opens a file for READ and places the cursor at the beginning of the file.
FOR APPENDING: Opens the file for writing and places the cursor at the end of file. If the file does not exist, it is generated.
BINARY MODE: The READ or TRANSFER will be character wise. Each time n characters are READ or transferred. The next READ or TRANSFER will start from the next character position and not on the next line.
IN TEXT MODE: The READ or TRANSFER will start at the beginning of a new line each time. If for READ, the destination is shorter than the source, it gets truncated. If destination is longer, then it is padded with spaces.
Defaults: If nothing is mentioned, then defaults are FOR INPUT and in BINARY MODE.
PROCESS FILE:
Processing a file involves READing the file or Writing on to file TRANSFER.
TRANSFER Statement
Syntax:
TRANSFER <field> TO <file name>.
<Field> can also be a field string / work area / DDIC structure.
Each transfer statement writes a statement to the dataset. In binary mode, it writes the length of the field to the dataset. In text mode, it writes one line to the dataset.
If the file is not already open, TRANSFER tries to OPEN file FOR OUTPUT (IN BINARY MODE) or using the last OPEN DATASET statement for this file.
IF FILE HANDLING, TRANSFER IS THE ONLY STATEMENT WHICH DOES NOT RETURN SY-SUBRC
READ Statement
Syntax:
READ DATASET <file name> INTO <field>.
<Field> can also be a field string / work area / DDIC structure.
Each READ will get one record from the dataset. In binary mode it reads the length of the field and in text mode it reads each line.
CLOSE FILE:
The program will close all sequential files, which are open at the end of the program. However, it is a good programming practice to explicitly close all the datasets that were opened.
Syntax:
CLOSE DATASET <file name>.
SY-SUBRC will be set to 0 or 8 depending on whether the CLOSE is successful or not.
DELETE FILE:
A dataset can be deleted.
Syntax:
DELETE DATASET <file name>.
SY-SUBRC will be set to 0 or 8 depending on whether the DELETE is successful or not.
Pseudo logic for processing the sequential files:
For reading:
Open dataset for input in a particular mode.
Start DO loop.
Read dataset into a field.
If READ is not successful.
Exit the loop.
Endif.
Do relevant processing for that record.
End the do loop.
Close the dataset.
For writing:
Open dataset for output / Appending in a particular mode.
Populate the field that is to be transferred.
TRANSFER the filed to a dataset.
Close the dataset.
Regards
Anver
if hlped pls mark points

Updating product revenue close date based off opportunity close date

We do not use the product revenue close date, only the opportunity close date. We need to get the fiscal month of the opportunity close date but we have several reports the need to use the opportunity product history area and that does not contain the fiscal month for the opportunity. If we did a combined report, we cannot offer the user any prompts.
Does anyone know how to get the opportunity close date fiscal month from the opportunity products area? Is there a way to update the product revenue close date when the opportunity close date it updated?
Thanks

Hi David,
In the universe you describe you have the opportunity 'Close Date'. Use a 'case-when' expression to create the 'Fiscal Month' you need.
Other than that you can use the JoinFieldValue function in the application to retrieve the opty close date, but that will require you to update product revenue for it to trigger which probably won't work for you.
Good luck.

"Expected Close" date needs to be 30 days from opened on day

Hi all,
We are trying to auto-populate an opportunity field ("expected close") with a date that would be 30 days in the future from the opportunity field "opened on" date. We have the opened on date already set so that it auto-populates with the date that a new opportunity is created.
This is what we have tried so far in the opportunity field edit area:
[<CloseDate>]=Today()+30
Any ideas as to why this isn't working, and ideas on how to make it work are appreciated!!

Yes this works.
Go to the Admin Section, Application customization, pick the field that you want to update (in our case Opportunity),
Click Opportunity Field Set-up, pick the field that you will update (in our case Close Date) and click "edit".
In the Default Value add this: Today()+30 (or however many days you want (in our case "30"days from created date))
click "Save"
Log out and log back in to see if update has happened.
GOOD LUCK!!

Opp Close Date - Quarters should be in Company Fiscal Year format

Hi,
I have to design report to calculate No of Opp Closed in Current Quarter and Last Quarter both according to Fiscal Year format.
Now, when I see Report 'Opportunity Analysis' for Data Source 'Opportunity Header and Item', Key Figure 'Close Date' has hierarchical date values (Quarter, Year Quarter etc) same as Calender Year.
For Example.
If Close Date = 15 Jan 2014, then system shows Quarter = Q1 and Year Quarter = Q1/2014. Meaning it is same as Calender Year.
Now, Company Fiscal Year starts from previous year Aug to July. So 15 Jan 2014 should be Quarter = Q2 and Year Quarter = Q2/2014.
Similarly, If Close Date = 10 Sept 2013, then system shows Quarter = Q3 and Year Quarter = Q3/2013. Meaning it is same as Calender Year.
Now, Company Fiscal Year starts from previous year Aug to July. So 10 Sept 2013 should be Quarter = Q1 and Year Quarter = Q1/2014.
To achieve Date hierarchical values in Fiscal Year format, Please let me know if I need to do any config OR if I am missing something OR I can achieve in fiscal format by creating new Key Figure.

Alim,
As per my knowledge I did not find any setting where you can change the Calendar Fiscal Year in the system.
But what you are trying to achieve can be done in a different way.
If I understand your requirement right if you have 10 Opportunities in Jan 2014 you should see them as Q2/2014 instead of Q1/2014. What you can do is you can create 4 Restricted Key figures for 4 Fiscal quarters , i.e Aug to Oct -- Q1. Sept to Jan--Q2 , Feb to Apr --Q3 , May to July -- Q4 . Then Hide the original Key figure and make these 4 Key figures available in your report.
So if a user searches for Jan2014 the Key Figure Q2 will have some values not Q1. Try this.
This is a round about solution which might work. Quarterly search is not possible in this case as the system is still assuming Jan2014 as Q1 but not Q2 what you did above is just masking of Q1 as Q2 in your report.
Hope this helps you.
Thanks
Pavan.

Last payroll offcycle close date/time

Hi Experts,
i need to write a function module to determine the last payroll off cycle close date/time.Can anyone suggest as to which tables i should be using to retrieve the relevant data.
Thanks

Try to read IT0267 records , this might Help . Also go through IT 221

Report on Opportunity Close Date Changes

I would like to create a report showing all deals that have had changes made to the Close Date. I am trying to create it from the Pipeline History section of the Analytics, but I am not sure which fields I can use, if any.
Any suggestions?

That is a very creative solution, Dale. I do have a couple of "what ifs" for you.
What if the Close Date is 10/30/2007... I change this to 10/15/2007 - a change of -15 days. Then I realize that I meant to change it to 11/15/2007 and changed it again. Would this create a problem for the report since the change amount would now show a 30-day change when it is really a 15-day change?
Another scenario has the date change twice in one week, between times that the report is run. The original date of 10/30/07 changes to 11/15/07 and then the next day changes to 12/15/07. How does this affect the report?
When we get to the point that the audit trail becomes reportable, this problem is solved. Until then, it is quite the puzzle. I think your solution potentially solves part of the problem, but depending on how much that date field actually changes and how often you run your report and which fields are needed in that report, it could return misleading data as well.
This is a very interesting problem. Dale has come closest to a solution so far. Any other suggestions for DavidG? I am drawing a blank on it so far.

Report on Opportunity Close date forecast Quarters

Hi,
we have created a custom report with fields from the Forecast section in Reporting including the Opportunity close date, and under the 'Close Date' we have put the Fiscal Quarter. However it is coming out wrong in some cases, so i added the 'Date' under the Close date section and not the opportunity section and it is different to the Close date on the opportunity. Can someone tell me what this 'Date' refers to?
Thank you

That is a very creative solution, Dale. I do have a couple of "what ifs" for you.
What if the Close Date is 10/30/2007... I change this to 10/15/2007 - a change of -15 days. Then I realize that I meant to change it to 11/15/2007 and changed it again. Would this create a problem for the report since the change amount would now show a 30-day change when it is really a 15-day change?
Another scenario has the date change twice in one week, between times that the report is run. The original date of 10/30/07 changes to 11/15/07 and then the next day changes to 12/15/07. How does this affect the report?
When we get to the point that the audit trail becomes reportable, this problem is solved. Until then, it is quite the puzzle. I think your solution potentially solves part of the problem, but depending on how much that date field actually changes and how often you run your report and which fields are needed in that report, it could return misleading data as well.
This is a very interesting problem. Dale has come closest to a solution so far. Any other suggestions for DavidG? I am drawing a blank on it so far.

Validating Opportunity close date

I was requested to create a validation for Opt. Close Date - Something like: If changed from the previous value it should be in the same quarter. Other than that it would be invalid.
I still trying but started using PRE(JulianQtr([<CloseDate>])) and do get syntax error about invalid name in expression... I suppose I should use PRE('<xxxxxx>') - so that means I cannot use PRE(JulianQtr.... ?
I'd appreciate any help.
Txs.
Antonio

Hello,
I am trying to validate the Opt. Close Date using:
(JulianQtr[<CloseDate>] - JulianQtr(PRE('<CloseDate>'))) <> 0
(JulianQtr[<CloseDate>] - 1 < JulianQtr(PRE('<CloseDate>')))
Both expressions are ok in the syntax checker but during opt field validation there is an error message about CSSString does not support '-'
So it seeems that somehow JulianQtr is returning a string value that cannot be used in expressions.
Pls. I'd appreciate any help.
Txs.
Antonio

Close dates profile

I'm trying to use custom.pll to override a value populated on the standard sale form.
When a user selects a Sale stage I want to overide the default close date profile for one of these entries in the LOV.
I can see that the block status has changed but when I check for the Sales tabpage and block_status = Changed these do not fire until I click into a field which does not have a LOV attached (total amount). Any Ideas?
Regards
Chiw

Hi Victor,
My doubt is you are saying 'On the 31/01/2010 these two positions should contribute to the coupons due', but when you bought the bond the coupon was not delivered so how will it contribute to the interest on 31/01. So effectively only the repo will contribute to the coupon interest and the bond will not contribute to the interest due on 31/01 because the next coupon was not delivered with bond purchase.
Please correct me wrong if the below case is what is your requirement
Book close date is 21/01, coupon payment date is 31/01.
Last coupon payment was on 31/07.
You purchase a bond on 19/01. This should contribute to the coupon payment on 31/01. Hence choose next coupon delivered so that you will pay accrued interest for the period from 01/08 till your purchase date and this bond purchase will have a coupon payment on 31/01.
Next you purchase a bond on 22/01. This should not contribute to the coupon payment on 31/01. Hence choose next coupon not delivered so that you will receive the accrued interest for the next 10 days. Now there will be no impact on the interest due on 31/01 because of this purchase. But from next interest payment onwards you will have impact because of both the purchases.
If this is what is your requirement then you need not have a -10 calculation date at all. You can have normal calculation date and when you make purchase you can make the changes depending on the book close date.
Regards,
Ravi

GL Account Start date and Close date

Hi,
Is it possible to maintain start date and close date of a GL account
Thanks & Regards
Radha

Requirement is, from a specific date the GL account should allow for posting and in the same way the GL account should not allow for posting for a specific posting.
So is it possible to give validity period for a GL account

When is the close date to when iOS 7 comes out?

I need a close date like i know iOS 7 comes out in the fall (August) but can someone give me like a date? From like a certain day to another week? Please?

User to user forum.
Apple have not announced a specific date.
You already know as much as any of us do-sometime in the Fall.
Fall runs from September 3rd until November 21st here in the US.

BW 0CS_ORDER CLOSE DATE

Similar Messages

Maybe you are looking for