Reg: CO_ORDER Archiving

Dear All,
For Archiving using CO_ORDER Object, the Write Program of it doesnot have the Date/Year Field.
But, we need to archive only those document from 1998 to 2006. the rest should not be archived.
How can this restriction be included while archiving ?
Any clues ???
Regards,
Deepu.k

Hi Deepu,
Have you tried to limit by customizing the residence time in application specific customizing?
If you set the appropriate residence time in application specific customizing, then you need not limit the time period in the write program variant.
refer this for CO_ORDER application specific customizing:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/ae/bb963457889b37e10000009b38f83b/frameset.htm
Thanks,
Naveen

Similar Messages

There is still a purchse order commitment for ORD X for CO_ORDER archiving obj

Dear Experts,
I am facing issue for CO_ORDER archiving object. I am getting error saying like
" there is still a purchase order commitment for ORD 200060" and
"order 200060 still has at least one purchase order that you need to do".
screen shot attached for reference
so Please help me to solve this issue.
Thanks in advance,
Ningappa S M

Hello Manju Sir,
Now that issue setting of deletion indicator is got successful. I mean I set residence time 1 as 0 and I tried to archive and I got successful. but I am facing the issue saying " there is still a purchase order commitment" , "there is a still Purchase requisition assigned to order" and
"still has at least one purchase order that you need to delete" etc for all orders when i set residence time 1 as 39 months (even i tried by setting the residence time 1 as zero i am getting the same error messages) and residence time 2 as 0. for these orders deletion flag itself is not getting set. so please help me for this.
Thanks,
Ningappa

CO_Order Archiving

We need to remove some internal orders which were prematurely created for our new fiscal year but will not be used after all due to changes to our chart of accounts paradigm. The obvious way to do this is to close and archive them off the system, and we have been attempting to simulate this processing in our development system prior to trying in our production system. The relevant archive object is CO_ORDER.
The internal order we are working with is closed, but is not picked up by the archive process. The archive process is configured that it doesn't require the order type of this order to remain on the system for any length of time after being closed. The order has no financial document postings, no PO's, no PR's.
Does anyone have any suggestions for determining why the order is being dropped (excluded) from the archive? I am new to archiving and do not know how to approach this problem.
Thank you,
Bob Unger

Hi Bob,
When there is no status I0013 for the internal order in table JEST, it means that Deletion Indicator (DLT) is not set for the order. To be able to archive internal orders the deletion indicator flag has to be set. The preprocessing program RKOREO01 is used to set the deletion indicator for the internal orders. You can access the preprocessing program via TA: SARA.
Your steps to archive CO_ORDER has to be as follows
1. Set Deletion Flag and Deletion Indicator by running preprocessing program available for CO_ORDER via SARA
2. Run the archiving job
Note: Deletion flag need to be set before you can set Deletion Indicator.
Refer the following link (SAP Help) for more details on archiving CO_ORDER
http://help.sap.com/saphelp_erp2005vp/helpdata/en/ae/bb963457889b37e10000009b38f83b/frameset.htm
Hope this helps.
Cheers,
Samanjay

Reg Mobile Archive Converter (Fileds are disabled)

Hi All
I have configured the MI server and is working fine. Only problem I face is, few fields in the Mobile Archive Converter are disabled and there is no application types found in the "Application Type" drop down. So I am not able to convert the war file to SDA. Since MTT applications are provided with sda I was able to deploy them successfully. But I would like to sovle this issue to convert other application war files.
I went throught the solution given in the forum. I have all rights assigned to the user I use, and also tried with the j2eeadmin, it is the same.
The fields disabled are
-Runtime
-Operating System
-Processor
-Language
-No application types found in "Application Type" drop down.
Help would be appriciated.
Thanks
Raj

Hi Rajesh,
Please check if user logged on NWA has the following UME permissions.
1. ArchiveConverter
2. ACLAdministration
This you can check via -: http://serverID:portnumber/useradmin
Search for the role assigned to logged on NWA user and check if the above 2 action assigned that role or not.
Is ArchiveConverter displaying any message?
If yes and the message is "can not read the initial settings from middleware" then Please check the settings of SAPJRA.
Settings you can find in SDN check my all posts.
Regards,
Satyendra

Reg : Data Archiving

Dear all
1) I have to retrieve a purchase order which was archived some time back from the archived files.
2) Once it is archived, I have to take a print out of the purchase order data and have to create pdf file using the script MEDRUCK.
Coould anyone suggest me in this regard?
Regards
Abhilash.

Hi,
most probable there is no easy cost free way.
There are two approaches. The first one is very simple. Do not archive MM_EKKO. The second option is to start a project: buy & implement PBS-Software (module CMM).
Regards
Walter Habich

CO_Order cannot be archived

We have CO_Order that have the delete indicator set under the old SAP
version 3.1. These orders have status DLT.
We have since moved to version 4.7, and would like to actually archive
these orders, but the system will not perform the archive for these
orders.
The system kept giving us message that the order is flagged
as "deleted" (and it has been "deleted" for a long time, because we
upgraded from version 3.1 to 4.7 in 2004), so we should be able to
archive these. But these orders just don't get archived.
To be clear, the question is: how do we archive CO_Order under version
4.7, when the deletion indicator has been set under version 3.1?
Any ideas on how we can fix/continue with this is greatly appreciated.
Thank you,
Suri

Hello,
If residence time 2 is 1 month, have you waited 1 month since setting the delete indicator before running the archive write job?
Here is an example archiving scenario:
residence time 1 = 1 month
residence time 2 = 1 month
You would first need to run the pre-processing job to set the deletion flag.
You then need to wait 1 month and run the pre-processing job AGAIN, to set the deletion indicator.
You would then need to wait 1 month before running the archive write job.
SAP Help Text on this:
Checks for Internal Orders (CO-OM-OPA)
Because the create archive program only selects orders that can be deleted, the criteria for deleting data is the same as for archiving data.
Internal orders have a deletion flag and a deletion indicator. Both are set by task functions.
Setting and deleting the deletion flag
You activate or reset the deletion flag for an internal order in the master data maintenance. If you set the deletion flag, the system checks whether the order can be deleted. Normally, you can only set the deletion flag if the order balance is zero. The following are exceptions:
Statistical orders
Orders for which the settlement profile is set up so that the actual costs are not to be settled or do not require settlement.
Setting the deletion indicator
Before you can set the deletion indicator, you need to set the delete flag. Residence time one must also have expired. You cannot reverse the deletion indicator once it is set.
You can set both the deletion flag and the deletion indicator in mass processing. In the Internal Orders menu, choose Tools ® Archiving ® Orders and then Preparation.
This process only archives orders for which the deletion indicator is set and for which residence time two has expired.
Both the residence times are part of the order type. You can change them in the implementation guide for internal orders by choosing Order Master Data ® Define Order Types.
Hope this helps.
Regards,
Karin Tillotson

Reg : Archiving of Internal Order

Hai Friends I am working on Archiving of Control Orders(Internal Orders) using KO02.
Archiving can be done only when deletion flag is set for Internal Order.
My issue is I want to set deletion flag for the Internal Order without going into the TCode KO02
and setting deletion flag.
Is there any other option for doing this.....

unless i am very much mistaken, internal orders follow the same algorithms as service orders or production orders, so you can set the deletion mark/flag using the archiving preproc. tx. SARA -> CO_ORDER -> PREPROC -> create variant. check whether you have to set times of residence in the configuration of the order type.

Tables not archived with CO_ORDER

Hi All,
CO_ORDER is the archiving object for archiving orders in CO
The following tables though they are listed in DB15 transaction are not getting archived with CO_ORDER but the table entries are deleted while running the delete program pertaining to CO_ORDER. These tables however are getting archived and deleted with CO_ITEM archiving object with object type ORD
The list of tables that are getting deleted are COBK,COBK_INDX,COEJ,COEJL,COEJR,COEP,COEPB,COEPL,COEPR.
If CO_ORDER object alone has to be archived, then these tables will not get archived but will be directly deleted.
Is there any sequence in archiving CO_ITEM and CO_ORDER?
Any pointers to the same will be helpful.

Hi,
Refer to the following note and its referenced corresponding notes for further information into this issue.
Note: 110923 Archives cannot be read or accessed
In addition, also refer to the following note that provides further clarity on the use of archiving and analysis (especially the information in relation to Programs RARCCOA1, RARCCOA2)
Note: 138688 Archiving/Controlling: table analysis
If this is an issue that the archive files for CO_ORDER are no longer available (Deleted), then please refer to the following information:
If you run the Analysis Program RKAARCS1 and the selection for the archive files shows a 'lightning bolt' this means the files are not accessible.
You can then check the archive information structures for CO_ORDER and if they are built. If they are not built there will be a 'red light' which indicates to build the structure via transaction SARI and Status. This is not possible if the Archive Files are not available though.
You will either have to restore the Archive files or Create a new Archive file. Care should be taken when you create Archive files that they are stored in a secure location and backed up on a seperate schedule than your normal backup.
I hope this information helps you get the results you are seeking.
Kind Regards,
Brendan
Edited by: Brendan O'Brien on Sep 2, 2008 2:21 PM

Reg Archive files

I want to know where the archive files will be stored, is it in application server, if i use the function module SUBST_GET_FILE_LIST, can i fetch the files for a particular directory, as i am able to fetch application server files, but i want to know whether i can fetch archive files.
Thanks & regards.
venkat.

Venkat,
Archived files are normally stored in External storage devises. Generally data which is old and not very frequently acessed is archived, to improve the afficiency of the SAP R/3 system.
Yes you can retreive archived files. There are standard programs to retrieve archived files.
For eg: RM06ER30 to retrieve archided Purchase Documents etc.
a Basis consultant plays the significan role to manage the storage decises such as providing ACESS to the archived data in external storage devises.
Hope this explanation of mine helps you.
Murthy.

Reg:File adapter archive Directory

Dear team,
Our requirement is to read a csv file from a directory and archive the file in archive folder specified in the file adapter.
If any exception is caught,then we need to read the archieve file from archive directory rename the archive file with source file name and place it in source directory.
On the receive activity we are able to get the source file name and source file directory.
<receive name="Receive1" createInstance="yes"
variable="Receive1_Read_InputVariable" partnerLink="fileRead"
portType="ns1:Read_ptt" operation="Read">
<bpelx:property name="jca.file.FileName" variable="srcFileName"/>
<bpelx:property name="jca.file.Directory" variable="srcDrFolder"/>
How to get the archive file name and archive file directory from the receive activity so that we can store in local variables.
Pls do help.
Thanks

Hi,
Another way you can accomplish your scenario. Instead of deleting or archiving in beginning just move the file from inbound to archive location after business flow completion.
In case of error, the file will remain at original position as moving operation is at the end.
First read the file using read operation, then at the end create a file adapter with sync read operation. Change the entries in .jca generated with below sample.
Sample jca file.
<endpoint-interaction portType="SynchRead_ptt" operation="SynchRead">
<interaction-spec className="oracle.tip.adapter.file.outbound.FileIoInteractionSpec">

<property name="SourcePhysicalDirectory"
value="srcdir"/>
<property name="SourceFileName" value="abc.txt"/>
<property name="TargetPhysicalDirectory"
value="targetdir"/>
<property name="TargetFileName" value="abc.txt"/>
<property name="Type" value="MOVE"/>
</interaction-spec>
Then,in you bpel flow at the invoke for sync read add these two properties.
<bpelx:inputProperty name="jca.file.SourceFileName"
variable="varInputFileName"/>
<bpelx:inputProperty name="jca.file.TargetFileName"
variable="varArchiveFileName"/>
<bpelx:inputProperty name="jca.file.SourceDirectory"
variable="varInputDirectory"/>
<bpelx:inputProperty name="jca.file.TargetDirectory"
variable="varArchiveDirectory"/>
- It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
Thanks,
Durga

Archived data - reg.

Hi All,
When I try to retrieve the archived documents i am not able to view customer name and number in the report. This is an issue raised by the user. Kindly advice me in this regard.
Regards,
P.Krishna Chaitanya

Hi Jorge,
I think your problem may be coming here kindly check this scenario
Execute transaction code FSE2 and select the "Financial Statement Version" used in reporting for the report in transaction code KE30 and then execute.
2. Open up the P&L hierarchy until you get to the Sales section. Click on the change icon and add the unassigned GROUPS SALES G/L account number to under the Sales of Goods hierarchy. Save your entries.
Go back and execute transaction code KE30, GROUPS SALES should no longer be under "Unassigned".
Hope this helps you
Prem

PM Notification archiving -clarification -reg

HI,
While planning for PM notifications archiving , io the preprocessing step of the tcode SARA , we dont find any reference date .
We need to archive notification which are changed before two years
we can take the details from QMEL like table and input in SARA , but going forward we need to schedule back ground jobs for the notifications archiving
do we need to do customization soem where to get the option of date here in the preprocessing stpe ?
now we have only
notification type
notification number
equipment
functional location
where as in the case of PM orders (object :PM_ORDER) we have the DLFl date or change date as reference
pl suggest
regards,
Madhu Kiran

Hi,
For PM Orders and Notifications two flags need to be set: deletion flag and deletion indicator.
For PM Order, the pre-processing variant can set both: deletion flag and deletion indicator.
For PM Notification, the pre-processing variant can only set the second one: deletion indicator. Hence, you can either manually set the deletion flag or create a custom program to set this deletion flag for you. Then SAP will analyse (in the pre-processing program), those notifications flagged for deletion and set the deletion indicator if possible.
After this, the write archiving program will pick up those notifications with deletion indicator set and archive them.
Hope this makes sense now.

Reg archiving to the SAP DMS server

Hi All
I have a requirement, I am building an RFC for the PORTAL backend. Currently the front end is generating the PDF for the vendor master. They will be sending the PDF as an XSTRING fromate to my BACKEND RFC. Then i need to convert this XSTRING to Binary -> Binary to PDF and archive it to the SAP DMS server.
Since i am new to this particular requirement . I need a sample code or some idea how to build the logic based on this requirement. Please suggest is there any better way to handle.
Portal Frontend - > Xstring - > Backend RFC ( ABAP Side) - > Archive to SAP DMS server.

Dear ,
i am facing such type of scenerio .
did u solve ur problem ?
i f so please favour me.

Archiving of Workflow items and Data stored - Reg

All gurus,
I am working on ECC 6.0 with the below system:
SAP_BASIS 700 0015 SAPKB70015 SAP Basis Component
SAP_ABA 700 0015 SAPKA70015 Cross-Application Component
I understand that not all the data that is available in the regular workflow log will be archived. But, I'm not able to find any information guidelines by SAP regarding what information will be saved and how this criteria of selecting the information being archived is done and where.
Can anybody tell me if there is any information regarding the above. Coz, this information archived(including the workflow and each ste (task) container data) is being inconsistent among various workflow logs.
So, it would be really helpful if anybody can share their experience and give some suggestions on this data storage selection.
Thanks in advance,
venu

Closing the thread due to no response.

Reg : Blocking and archiving of IDocs

Hi All,
          Could anyone please let me know when does the need arise to block an IDOC?
          I heard it some where that for some type of errors we can not reprocess the idoc and so they will block that and resend it once more.
         If anyone has worked on this type of issue, could you please give me some information?
And one more thing is regarding the Archiving of IDOCS : Could nay one please let me know the importance of IDOC ARCHIVING and it's use?
Regards
Abhilash.

Hi,
Blocking Idocs most extensively is used in master data, where we block the errored IDocs, rectify the error and replicate once again. Transactional data IDocs can also be blocked as per the situation.
With archiving, IDocs are archived in various tables in the database in order that the size of the tables could be reduced without losing any IDocs. The transaction used for archiving is, SARA where the archiving object selected in this case is "IDOC".
~ Bineah.

Reg: CO_ORDER Archiving

Similar Messages

Maybe you are looking for