Delivery archived

Hi,I checked the document flow of one billing document via t-code: VF03, and it shows as follows:
Document Date Overall processing status
. Delivery 1000514964 Archived <<<----
Invoice 90454051 06/08/15 Completed
. Accounting document 8600041838 06/08/15 Cleared
My question is, what's the meaning of 'Archived' to the delivery number 1000514964, what kind of operation could caused its status become to 'Archived'?
Please kindly help.
Best Regards.

Hi Ren,
It seems the delivery document 1000514964 has been archived/removed from database application data
and placed in archive file that can be accessed and analyzed at a later date/in the future.
For more information on application data archiving, please check this online document.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARC/CAARC_INTRO.pdf
Hope this will help.
Regards,
Ferry Lianto

Similar Messages

Delivery Deleted, Showing error when deleting sales order. R3, Oracle9i

Hi experts,
One of my users deleted delevery document and when he is trying to delete sales order it is giving error.
Also it is showing delivery archived. How to retrieve the document.
Thnx in advance

Hi Dhanush,
I suppose there is no need to run any consistency jobs for this issue(as per my understanding).
As specified above by Senthil just try first running //CCR for the LOC_PRODUCT with category as Sales Order (also tick the VBBE table option) and Purchase Order. I think this will solve your purpose. Also please make sure that the IMs for the LOC_PRODUCT is active.
Do let us know your findings on the same.
Thanks and Regards,
PP.

Billing doc cancelled

Dear Friends,
We are facing a major issue which is as follows:
A bill doc was cancelled. The doc flow of the original billing doc shows:
Delivery (Archived)-> Sale Invoice (Completed)-> A/cing doc (Not Cleared)
The cancelled doc is not coming in the above doc flow. What can be the reason that cancelled doc is not coming in the doc flow?
On the other hand the doc flow of the Cancelled doc shows:
Delivery (Same as above) (Status Archived)->Cancel Inv (S1) Status- Missing export data. (Transaction is domestic). Here also the original bill doc is not coming in the doc flow of S1. However the original doc is coming in the Assignment field in the header of S1. Again what can be the reason? We also want to clear the A/cing doc of the original Billing document. How is this possible?
Is there any T.Code for displaying J1ID?
Plz hep to solve these issues.
Thank you very much.

Go to VA03, key in the sale order reference and check the document flow. Let me know whether you could see the original billing document that was cancelled. If not, check in copy control whether you have ticked the box "Update document flow".
Is there any T.Code for displaying J1ID?
What do you mean by this ?? J1ID itself is a standard TCode.
thanks
G. Lakshmipathi

Adding Libraries & External Library DC - Not able to import JAR Files

Hi,
I am trying to import the jar files to development environment.
The JAR file was added by following the steps mentioned in below blog :
/people/bala.krishnan2/blog/2006/09/25/bid-adieu-to-bots--using-captchas
Please find the error log below :
20100728065650 Info   :connected to deploytool via sdm protocol
20100728065651 Info   :deploy every archive associated to the buildspace: DP1_MSSTRK19_D
20100728065651 Info   :getting DC mss/eepro/salarydata from CBS for buildspace: DP1_MSSTRK19_D
20100728065651 Info   :Following SDAs were added:
20100728065651 Info   : 201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda
20100728065651 Info   :archives (201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda) for DC mss/eepro/salarydata were selected
20100728065652 Info   :Start deployment:
20100728065652 Info   :The following archives will be deployed (on http://sapdp1ci.zrh.swissre.com:53018)
20100728065652 Info   :/usr/sap/DP1/SYS/global/TCS/DEPLOYARCHIVES/201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda
20100728065652 Info   :starting deployment
20100728065652 Info   :errorhandling rule is switched from OnErrorStop to OnErrorSkipDepending
20100728065652 Info   :prerequisite errorhandling rule is switched from OnPrerequisiteErrorStop to OnPrerequisiteErrorSkipDepending
20100728065654 Info   :deployment finished
20100728065654 Info   :errorhandling rule is reseted
20100728065654 Info   :prerequisite errorhandling rule is reseted
20100728065654 Info   :Deploy log:
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: Start file transfer to /usr/sap/DP1/JC30/SDM/program/temp/201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: File transfer of /usr/sap/DP1/JC30/SDM/program/temp/201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda finished for 9 ms. Total file size is 1347307 bytes.
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: The SDM client uses an old SDM client API.
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: -
Starting deployment -
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: Error handling strategy: OnErrorSkipDepending
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: Update strategy: UpdateAllVersions
20100728065654 Info   :Jul 28, 2010 6:56:52 AM Info: Starting deployment prerequisites:
20100728065654 Info   :Jul 28, 2010 6:56:53 AM Info: Loading selected archives...
20100728065654 Info   :Jul 28, 2010 6:56:53 AM Info: Loading archive '/usr/sap/DP1/JC30/SDM/program/temp/201007280456510519_sap.com_SAP_MSS_1_sap.com_msseeprosalarydata.sda'
20100728065654 Info   :Jul 28, 2010 6:56:54 AM Info: Selected archives successfully loaded.
20100728065654 Info   :Jul 28, 2010 6:56:54 AM Error: Unresolved dependencies found for the following SDAs:
20100728065654 Info   :
20100728065654 Info   :1.: development component 'mss/eepro/salarydata'/'sap.com'/'DP1_MSSTRK19_D'/'31236'/'0'
20100728065654 Info   :dependency:
20100728065654 Info   :       name:     'temp/jxljar1'
20100728065654 Info   :     vendor:     'swissre.com'
20100728065654 Info   :
20100728065654 Info   :There is no component either in SDM repository or in Deployment batch that resolves the dependency.
20100728065654 Info   :
20100728065654 Info   :Deployment will be aborted.
20100728065654 Info   :Jul 28, 2010 6:56:54 AM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
20100728065654 Info   :Deployment will be aborted.
20100728065654 Info   :Jul 28, 2010 6:56:54 AM Error: Prerequisites were aborted.
20100728065654 Info   :Jul 28, 2010 6:56:54 AM Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
20100728065654 Info   :Deployment will be aborted.
20100728065654 Info   :end of log
20100728065654 Info   :End deployment:
20100728065654 Info   :
20100728065654 Info   :Summary of deployment
20100728065654 Info   :==> deployment finished for mss/eepro/salarydata (28979) with rc=12
20100728065654 Info   :deployment finished for buildspace: DP1_MSSTRK19_D
Please let me know how to fix this issue.
Thanks in advance.
Thanks and Regards,
Rashmi

Rashmi,
Following observations from the error log:
a) DC temp/jxljar1 is External Library DC; if I am not wrong.
b) Once the J2EE DC is deployed; automatically jxljar1 should also be loaded in server
Coming to the issue you are facing; plz let us know following points:
a) Are you trying to transport the content from one landscape to the other i.e. development to QA?
b) During what operation and in which unit(DTR/CMS/CBS);you are facing the issue?
Regards,
Ganga

EP + BW: Problems with user mapping in the portal

Hi,
I'm trying to connect the portal with the BW by using the report RSPOR_SETUP which is a step-by-step guide. The steps #1 - #11 seems to be ok but my problem is the 12th step, the user mapping/allocation maintenance in the portal.
There is an error emerging (in BW): System failure during call of function module RSWR_RFC_SERVICE_TEST (System failure indicates normally an authentication problem between ABAP and Java)
Another error is emerging by testing the connection in the portal. (System administration u2013 system configuration u2013 system landscape u2013 connection test: the first connection, the SAP Web-AS connection is ok but the second, connection test for connector, is not working.
Especially the connection to the backend system with the defined connector is not working. The output is: u201CConnection failure. Check that single sign on is correct configured.
On step 12 of the step-by-step guide I have to select a user in the portal, relate him to a system alias und maintain his technical username and password for the BW. I think here is the problem. Iu2019m able to select and save a system alias for the user, but Iu2019m not able to save his technical username and password. There is another error emerging (in the portal): u201CVerification of user mapping data for system SAP_BW failed, check credentials for errorsu201D, so Iu2019m not able to save the username and password.
I think thats the my problem. the log file confirms that: "Did not find any existing logon data for principal...." & "No user mapping data available for principal...."
I hope my problem description is understandable.
Any ideas how I can solve the credentials problem to save the username and the password?
Thanks in advance.
Tan
Edited by: Tan Yildiz on Jul 22, 2009 1:26 PM

I could deploy some of the usage types, but there is an error regarding the BI-REPPLAN package. I think it's one of the very last errors that stands between me and a working EP - BI connection. There is a problem with the version. Could you check the log details, to find out more?
Thank you.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\BIP\JC02\SDM\program\log\sdmcl20090806164716.log]/>
<!PATTERN[sdmcl20090806164716.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Aug 6, 2009 6:47:16 PM Info: -
Starting validation -
Aug 6, 2009 6:47:16 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Aug 6, 2009 6:47:16 PM Info: Update strategy: UpdateLowerOrChangedVersions
Aug 6, 2009 6:47:16 PM Info: Starting deployment prerequisites:
Aug 6, 2009 6:47:18 PM Info: Loading selected archives...
Aug 6, 2009 6:47:18 PM Info: Loading archive 'D:\usr\sap\BIP\JC02\SDM\program\temp\BIREPPLAN04_0-10005889.SCA'
Aug 6, 2009 6:47:21 PM Info: Selected archives successfully loaded.
Aug 6, 2009 6:47:21 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'bi/plan/helpers/table2'/'sap.com'/'MAIN_NW701P03_C'/'2846642'/'0'
dependency:
 name: 'bi/alv/common'
 vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
 name: 'bi/alv/ui'
 vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM Error: Prerequisites were aborted.
Aug 6, 2009 6:47:22 PM Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:23 PM Info: -
Ending validation -

DI installation for NWDI

Dear Experts,
I have installed ECC/ EP on the same server and while installation not selected NWDI.
Now I want NWDI so that developer can work? How do I start with? What things needs to be installed?
Have checked the Service market place for download the DI packages from the link below
Support Packages and Patches
Support Packages and Patches" SAP NetWeaver" SAP NETWEAVER" SAP NETWEAVER 7.0" Entry by Component" Development Infrastructure
Development Infrastructure
ADOBE DOCUMENT SERVICES 7.00
BI META MODEL REPOSITORY 7.00
BI UDI 7.00
DI BUILD TOOL 7.00
DI CHANGE MGMT. SERVER 7.00
DI COMPONENT BUILD SERVER 7.00
DI DESIGN TIME REPOSITORY 7.00
From the above we can see there are 4 different things from DI side. So what needs to be downloaded to install the DI for the nwdi if not installed during the ECC installation?
Regard

Hi Jazz,
I think I have gone through the information you have provided. But I like to mention few details.
I have updated my JSPM till 12 and while selecting the Add on , the packages was not read.. It read from teh same option of Business package.. and when tried selecting hte 3 DI components, it gave error with DI_CMS. So I continued with the 2. and CMS is giving the error message as below.
Any information u would like to share?
root@sapdev # pwd
/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08
BATCHCONFIG_04.ERR
PerfTimes : loadNativeLayer: loading jperflib failed. /sap/sapmnt/DEV/exe/libjperflib.so: ld.so.1: java: fatal: /sap/sapmnt/DEV/exe/libjperflib.so: wrong ELF class: ELFCLASS64
BATCHCONFIG_05.ERR
PerfTimes : loadNativeLayer: loading jperflib failed. /sap/sapmnt/DEV/exe/libjperflib.so: ld.so.1: java: fatal: /sap/sapmnt/DEV/exe/libjperflib.so: wrong ELF class: ELFCLASS64
09/01/22 19:33:24 -    com.tssap.dtr.pvc.repository.RepositoryManager - LOGGING CONFIGURATION
09/01/22 19:33:24 -    com.tssap.dtr.server.servlet.WebdavMethod.tracePerformanceStatistics - LOGGING CONFIGURATION
09/01/22 19:33:24 -    /Applications/DTR/Propagation - LOGGING CONFIGURATION
09/01/22 19:33:24 -    com.tssap.dtr.server.servlet.WebdavServlet - LOGGING CONFIGURATION
09/01/22 19:33:24 -    SAP/BC_DTR - JDBCCONNECTOR
09/01/22 19:33:24 -    dtr - WEB
09/01/22 19:33:24 -    sap.com/tcdtrenterpriseapp monitoring configuration - MONITORING CONFIGURATION
09/01/22 19:33:24 - ***********************************************************
Jan 22, 2009 7:33:43 PM Info: End of log messages of the target system.
Jan 22, 2009 7:33:43 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 22, 2009 7:33:43 PM Info: Finished successfully: development component 'tc/dtr/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_C'/'1521448'/'0', grouped
by software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'
Jan 22, 2009 7:33:43 PM Info: Starting to save the repository
Jan 22, 2009 7:33:47 PM Info: Finished saving the repository
Jan 22, 2009 7:33:47 PM Info: Starting: Initial deployment: Selected development component 'tc/jdi/heartbeat/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_
C'/'1497030'/'0' will be deployed.
Jan 22, 2009 7:33:47 PM Info: SDA to be deployed: /sap/sap/DEV/DVEBMGS10/SDM/root/origin/sap.com/tc/jdi/heartbeat/enterpriseapp/MAIN_APL70VAL_C/0/149
7030/tcjdiheartbeat~enterpriseapp.sda
Jan 22, 2009 7:33:47 PM Info: Software type of SDA: J2EE
Jan 22, 2009 7:33:47 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 22, 2009 7:33:50 PM Info: Begin of log messages of the target system:
09/01/22 19:33:47 - ***********************************************************
09/01/22 19:33:47 - Start updating EAR file...
09/01/22 19:33:47 - start-up mode is lazy
09/01/22 19:33:47 - EAR file updated successfully for 117ms.
09/01/22 19:33:47 - Start deploying ...
09/01/22 19:33:48 - EAR file uploaded to server for 50ms.
09/01/22 19:33:48 - Successfully deployed. Deployment took 523ms.
09/01/22 19:33:48 -    Application : sap.com/tcjdiheartbeat~enterpriseapp
09/01/22 19:33:48 -
09/01/22 19:33:48 -    heartbeatJDI - WEB
09/01/22 19:33:48 -    sap.com/tcjdiheartbeat~enterpriseapp monitoring configuration - MONITORING CONFIGURATION
09/01/22 19:33:48 - ***********************************************************
Jan 22, 2009 7:33:50 PM Info: End of log messages of the target system.
Jan 22, 2009 7:33:50 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 22, 2009 7:33:50 PM Info: Finished successfully: development component 'tc/jdi/heartbeat/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_C'/'1497030'/'0'
, grouped by software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'
Jan 22, 2009 7:33:50 PM Info: Starting to save the repository
Jan 22, 2009 7:33:53 PM Info: Finished saving the repository
Jan 22, 2009 7:33:53 PM Info: Starting: Initial deployment: Selected software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117
061443''/'0' will be deployed.
Jan 22, 2009 7:33:53 PM Info: Finished successfully: software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'
Jan 22, 2009 7:33:53 PM Info: Starting to save the repository
Jan 22, 2009 7:33:56 PM Info: Finished saving the repository
Jan 22, 2009 7:33:56 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jan 22, 2009 7:33:56 PM Info: -
Deployment was successful -
Jan 22, 2009 7:34:00 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp
Jan 22, 2009 7:34:00 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63109
Jan 22, 2009 7:34:04 PM Info: Opened client connection to sapdev (IP address sapdev/10.150.203.95, remote port 63508)
Jan 22, 2009 7:37:23 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp
Jan 22, 2009 7:37:23 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63508
Jan 22, 2009 7:37:41 PM Info: Start logging to '/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08/OperateSDM_01.LOG'
Jan 22, 2009 7:37:41 PM Info:
Jan 22, 2009 7:37:41 PM Info: ==========================================
Jan 22, 2009 7:37:41 PM Info: =   Starting to execute command 'ping'   =
Jan 22, 2009 7:37:41 PM Info: ==========================================
Jan 22, 2009 7:37:41 PM Info: Sending "ping" command to the SDM server...
Jan 22, 2009 7:37:41 PM Info: Opened client connection to localhost (IP address localhost/127.0.0.1, remote port 63565)
Jan 22, 2009 7:37:42 PM Error: Wrong password supplied - Request for Logon rejected. Remaining logon attempts until SDM server will be shut down: 2
Jan 22, 2009 7:37:42 PM Error: SDM server is running, but authentication failed because of wrong password.
Jan 22, 2009 7:37:42 PM Info: Close client connection to localhost/127.0.0.1, remote port 63565
Jan 22, 2009 7:37:42 PM Error: Processing error. Return code: 104
Jan 22, 2009 7:39:12 PM Info: Start logging to '/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08/OperateSDM_01.LOG'
Jan 22, 2009 7:39:12 PM Info:
Jan 22, 2009 7:39:12 PM Info: ==========================================
Jan 22, 2009 7:39:12 PM Info: =   Starting to execute command 'ping'   =
Jan 22, 2009 7:39:12 PM Info: ==========================================
Jan 22, 2009 7:39:12 PM Info: Sending "ping" command to the SDM server...
Jan 22, 2009 7:39:12 PM Info: Opened client connection to localhost (IP address localhost/127.0.0.1, remote port 63590)
Jan 22, 2009 7:39:12 PM Error: Wrong password supplied - Request for Logon rejected. Remaining logon attempts until SDM server will be shut down: 1
Jan 22, 2009 7:39:12 PM Error: SDM server is running, but authentication failed because of wrong password.
Jan 22, 2009 7:39:12 PM Info: Close client connection to localhost/127.0.0.1, remote port 63590
Jan 22, 2009 7:39:13 PM Error: Processing error. Return code: 104
Jan 22, 2009 7:39:14 PM Info: Opened client connection to sapdev (IP address sapdev/10.150.203.95, remote port 63598)
Jan 22, 2009 7:39:14 PM Info: -
Starting validation -
Jan 22, 2009 7:39:14 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Jan 22, 2009 7:39:14 PM Info: Update strategy: UpdateLowerVersions
Jan 22, 2009 7:39:14 PM Info: Starting deployment prerequisites:
Jan 22, 2009 7:39:18 PM Info: Loading selected archives...
Jan 22, 2009 7:39:18 PM Info: Loading archive '/usr/sap/DEV/DVEBMGS10/SDM/program/temp/DICMS14_0-10003499.SCA'
Jan 22, 2009 7:39:24 PM Info: Selected archives successfully loaded.
Jan 22, 2009 7:39:25 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'tc/SL/CMS/PCS'/'sap.com'/'MAIN_APL70VAL_C'/'1535381'/'0'
dependency:
       name:     'tc/com.sap.tmw.clients/_ctsa_client'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'tc/di/scm/transport_api'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Jan 22, 2009 7:39:25 PM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Jan 22, 2009 7:39:25 PM Error: Prerequisites were aborted.
Jan 22, 2009 7:39:29 PM Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) select
ed. Select at least one.
Deployment will be aborted.
Jan 22, 2009 7:39:34 PM Info: -
Ending validation -
Jan 22, 2009 7:39:34 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp
Jan 22, 2009 7:39:34 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63598

Regarding SAP PSS Business package import into NW 2004s Portal

Hi All,
 I am trying to import the SAP PSS business package into the SAP NW 2004s portal. I initially tried the SAP PSS 3.0 package. I copied this downloaded business package zip file into the
Drive:/usr/SAP/trans/EPS/IN folder structure. I then went into the JSPM folder in the Drive:/usr/SAP/SAP SID/J2EE/JSPM folder to start the deployment of the business package.
I selected the new software component and No NWDI Control as there is no NWDI control. In the next screen, I selected the SAP PSS business package's version and hit continue to proceed to the next step.
But, I am getting stuck with an error "Error during validatiion of the dependencies of the selected Software components"
I checked the log file in the SDM folder and the log file has the following information:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[H:\usr\sap\EPT\JC01\SDM\program\log\sdmcl20060313201148.log]/>
<!PATTERN[sdmcl20060313201148.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Mar 13, 2006 3:11:48 PM Info: -
Starting validation -
Mar 13, 2006 3:11:48 PM Info: Loading selected archives...
Mar 13, 2006 3:11:48 PM Info: Loading archive 'H:\usr\sap\EPT\JC01\SDM\program\temp\SAPPSS02_0-2000121.SCA'
Mar 13, 2006 3:11:51 PM Info: Selected archives successfully loaded.
Mar 13, 2006 3:11:51 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'ep/pss/creamail'/'sap.com'/'MAIN_ERP05VAL_C'/'194412'
dependency:
 name: 'pcui_gp/xssutils'
 vendor: 'sap.com'
dependency:
 name: 'pcui_gp/xssfpm'
 vendor: 'sap.com'
2.: development component 'ep/pss/common'/'sap.com'/'MAIN_ERP05VAL_C'/'194415'
dependency:
 name: 'pcui_gp/xssutils'
 vendor: 'sap.com'
dependency:
 name: 'pcui_gp/xssfpm'
 vendor: 'sap.com'
Deployment will be aborted.
Mar 13, 2006 3:11:51 PM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Mar 13, 2006 3:11:51 PM Error: -
Deployment was aborted -
Mar 13, 2006 3:11:51 PM Error: Error while creating deployment actions.
Mar 13, 2006 3:11:51 PM Info: -
Ending validation -

I later downloaded the SAP PSS 2.0 to check and upload this content into the portal. But unfortunately, this also stopped at the same place with the same error.
Could anyone please check and let me know about this?
All the useful answers/suggestions will be rewarded.
Thanks,
Sunitha.

Sunitha,
Looks like you need SAP XSS.
go the service.sap.com, Downloads, Support Packages and Patches , Entry by Application Group,SAP Application Components, SAP ERP, SAP ERP 2004, Entry by Component,SAP XSS (Self Services).
-SG

Web Page Composer Link

Hi All,
Can anyone tel me the exact link from where Web Page Composer can be downloaded , My portal is running on SP12 .I have gone through SDN but could not find any pointers.
Points will be awarded for helpful answer.
Thanks
Pankaj

Hi Experts,
I am facing problem in deploying WPC in EP System. Here we have SPS20. and i am trying to deploy KMCWPC20_0-20002294.SCA but i am facing the below error.
Nov 9, 2010 7:17:23 PM   Info: -
Starting validation -
Nov 9, 2010 7:17:23 PM   Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Nov 9, 2010 7:17:23 PM   Info: Update strategy: UpdateLowerOrChangedVersions
Nov 9, 2010 7:17:23 PM   Info: Starting deployment prerequisites:
Nov 9, 2010 7:17:52 PM   Info: Loading selected archives...
Nov 9, 2010 7:17:52 PM   Info: Loading archive '/usr/sap/trans/EPS/in/JAVA_PATCH_20/KMCWPC20_0-20002294.SCA'
Nov 9, 2010 7:17:52 PM   Error: Exception occured during extractSingleFile: invalid entry size (expected 62533 but got 62532 bytes)
Nov 9, 2010 7:17:52 PM   Info: Selected archives successfully loaded.
Nov 9, 2010 7:17:52 PM   Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Nov 9, 2010 7:17:52 PM   Error: Prerequisites were aborted.
Nov 9, 2010 7:17:59 PM   Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Nov 9, 2010 7:18:06 PM   Info: -
Ending validation -
Could any body will give me suggesstion for this.
Thanks & Regards,
Arun

What are SDA and SCA

Hi this is seshu,
I have seen some material SDA and SCA what are those...can anyone explain ...Pls

Hi,
You require an SDA file to allow you to transfer the table definitions from the current Dictionary project to a database instance of the SAP DB. An SDA (Software Delivery Archive) is an archive file that represents a deployable unit of the Dictionary project
For more detail please refer this link
http://help.sap.com/saphelp_nw70/helpdata/en/50/842240852e8f5ce10000000a155106/frameset.htm
SCA i.e. software component archive are the consolidated software and deplolyable unit, when you use Development infrastructure for creating a software, you create SCAs of your software components and finally consolidate them into a single software.
Hope this helps you,
Regards,
Ameya

Deploying pdk, i have some trouble in sdm

hi
i download pdk6.0_60_3 for ep6.0sp4. the content of pdk
is the format of .sca. i want to deploy the .sca file by software delivery manager( /usr/sap/EPDEV/java/sdm/program/startSDM.sh ). when i choose the "add swc/sda/sca to deployment list", in the file box, i choose the pdk file "20040506.sca". then there is an error "/usr/sap/EPDEV/j2ee/j2ee_00/../../java/sdm/root/origin_sc/com.sap/pdk/6.30/work/Welcome.ear is neither a SWC (Software Delivery Catalog) nor a SDA (Software Delivery Archive). Please choose another file.".
i don't know how to work out it!

Hi,
the Welcome.ear is a WebDynpro archive. Do you have WebDynpro deployed on your EP?
Regards,
Armin

Regd-LM Service 701 and LM tool deployment dependancy in Solution Manager

Hi,
While Upgrading LM Service to 701 patch 4, i am getting a dependancy error. The log details are as follows,
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[E:\usr\sap\DSM\DVEBMGS10\SDM\program\log\sdmcl20090917072303.log]/>
<!PATTERN[sdmcl20090917072303.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Sep 17, 2009 8:23:05 AM Info: -
Starting validation -
Sep 17, 2009 8:23:05 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Sep 17, 2009 8:23:05 AM Info: Update strategy: UpdateLowerOrChangedVersions
Sep 17, 2009 8:23:05 AM Info: Starting deployment prerequisites:
Sep 17, 2009 8:23:08 AM Info: Loading selected archives...
Sep 17, 2009 8:23:08 AM Info: Loading archive 'E:\usr\sap\DSM\DVEBMGS10\SDM\program\temp\LMTOOLS04_1-10005881.SCA'
Sep 17, 2009 8:23:12 AM Info: Selected archives successfully loaded.
Sep 17, 2009 8:23:13 AM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'tc/di/cts/config/service/appl'/'sap.com'/'MAIN_NW701P04_C'/'2969406'/'1'
dependency:
 name: 'tc/di/cts/common'
 vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Sep 17, 2009 8:23:13 AM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Sep 17, 2009 8:23:13 AM Error: Prerequisites were aborted.
Sep 17, 2009 8:23:13 AM Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Sep 17, 2009 8:23:14 AM Info: -
Ending validation -
Kindly help me to resolve this issue.
Thanks & Regards,
Vaishali.K

Hi,
LMSERVICE03P_4-20004805.SCA Patch 4 for SOLMANDIAG 7.01 SP03 (Software package in production process (See note 1120196)
Hope this helps.
Feel free to revert back.
-=-Ragu

CMS and CTS+

Hi all,
I want to know the difference between CTS+ and CMS. Is there any additional advantage provided by CTS+ over CMS? Also what is the difference in the procedure to transport IR and ID objects in CMS and CTS+.
Any links to documents related to transporting IR , ID objects via CMS and CTS+ will be very helpful.
Regards,
Santosh

Hi,
What is CTS+ and why is is introduced:
The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape.
The XI use case for CTS+ introduces a new transport handling mechanism that offers tighter integration for the transport of ABAP, Java, and Integration Builder objects (Integration Repository and Integration Directory) using the Change and Transport System (BC-CTS) functionality.
As your XI system requires both the ABAP and the Java stack of the SAP NetWeaver Application Server, the following transport tools are available after installation:
u2022
The ABAP transport environment (BC-CTS)
u2022
The file export and import mechanisms or CMS integration to transport Repository or Directory objects in your transport landscape
In addition, you might also have to transport Java development objects by using the SAP NetWeaver Development Infrastructure itself.
The enhancements to CTS in combination with the SAP Solution Manager Change Request Management (ChaRM) address the following issues:
u2022
Synchronized transports for mixed systems (ABAP & Java)
u2022
A unified application for mixed system landscapes
u2022
Tracking of non-ABAP transports including Change Request Management
For your XI landscapes there will be one central transport environment with CTS+ where you can manage all XI-relevant transport objects from a single entry point.
This how-to guide describes the configuration settings you must make in the CTS+ system and XI systems. The functionality must be set up according to the release version of the integrated XI system. The two configurations will be described separately:
u2022
Configuration setup for releases prior to SAP NetWeaver 7.0 SPS12 (also for SAP NetWeaver 2004 SPS14 and higher).
u2022
Configuration setup for release SAP NetWeaver 7.0 SPS12 and higher.
Refer the link for CTS+ step by step method of transport:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6
http://help.sap.com/saphelp_nw04/helpdata/en/03/dcb6b6048711d3b42a00609419f767/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
CMS is generally used to transport Java development objects. The XI Integration Server uses CMS to transport Integration Server content. When the Integration Server uses CMS to transport XI Content, no Component Build Service (CBS) or Design Time Repository (DTR) is used and can therefore be switched off. If you want to transport Integration Server content and Java developments (Java proxies or adapter modules), the CBS and DTR must be running.
If you transport Java developments, you should keep in mind that deployment of Java code can destabilize the runtime environment. Therefore, it is beneficial to install CMS on a separate server, as described in SAP Note 737368 for NWDI.
In this How-to Guide, CMS is installed together with an Integration Server system in the development environment. The advantage of this approach is that you have fewer steps in user management and CMS cannot influence the runtime of a productive environment.
With the enhancements of the SAP NetWeaver Change and Transport System (CTS for short, or CTS+ respectively, if specifically the enhanced capabilities are meant), available with SPS12 of SAP NetWeaver 7.0, the CTS has been enhanced to handle any type of object that can be transported in an SAP system landscape. Therefore, an administrator of your ABAP system can now also manage the transports for the non-ABAP parts of your system landscape.
You can now use CTS to transport (almost) arbitrary objects in an SAP system landscape with transport orders of the Transport Organizer:
u2022
Enterprise Portal archives (EPAs)
u2022
Exchange Infrastructure objects (TPZs)
u2022
Software component archives (SCAs)
u2022
Software delivery archives (SDAs)
u2022
Enterprise Application Archives (EARs)
u2022
ABAP objects
Development objects will be deployed according to their application type. Objects in a single transport order can be a mixture of all types u2013 however that only makes sense, if both are intended for the same system because transport paths are defined in the transport domain controller system.
CTS+ and usage type PI (SAP NetWeaver Exchange Infrastructure, XI)
o
If you are not using the Change Management Service CMS of the NWDI, you should seriously consider using CTS+ for your XI transports (CTS+ & SAP NetWeaver usage type PI).
o
If you are already using the CMS, you should postpone any planned migration to use CTS+ up to availability of SAP NetWeaver 7.0 SPS 13 , where integration will be enhanced futher.
o
In any case you should evaluate the enhanced CTS options of SAP NetWeaver 7.0 comming with SPS 12 and extensions planned with SPS 13/14 for XI transports u2013 in the mid and long term CTS+ is the best practice recommended by SAP for XI tranports.
CMS for SAP Exchange Infrastructure
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
Configuration of CMS in Central NWDI & SLD to transport XI objects
Configuration of CMS in Central NWDI & SLD to transport XI objects
How to Use CMS in XI 3.0.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
CMS based transport in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Regards,
Phani

Delivery document flow show as a Archived,

Dear Experts,
My some of delivery document show in document flow as a archived, I want to know, Why delivery document archived,
I also want to not list of archived delivery document,
Can anybody give me t.code for list of delivery document archived,
Regards:
Happy

Hi,
Are these delivery actually archived by archiving job? Is there any subsequent document after the delivery?
Technically, if an delivery doesn't exist in LIKP table, but it exist in VBFA table, it will show "archived" in document flow.
As of why the delivery doesn't exist in LIKP, there could be two possibilities:
- it's deleted by archiving job.
- for unknown reason, it's gone.
To know why it's gone, it's necessary to reproduce the issue. If you can reproduce, please raise a message to SAP support.
What you need to do:
- If this delivery is really archived by your archivng job, you should also archive the preceding sales document.
- If this delivery is not supposed to be archived, but misisng, you need ot delete this dummy entry from VBFA table, and then recreate delivery.
To get a list of this kind of archived document, there is no standard report or transaction to do that. You need to write your own report to do that. As mentioned above, technically, if delivery exist in VBFA but doesn't exist in LIKP, it will be displayed like that. You may selecting VBFA and LIKP tables to get your list.
Regards,
Harry

How to get Status of Archived Delivery Document line item

Hi Folks,
I want read the Status of line item of archived delivery document.
As delivery is archived, it is not found in LIKP/LIPS. So I got the archived delivery document from VBFA table.But this does not contain the status field.
Is there any program or Function modules which reads this status.
Please help.
Thanks in advance.

Check field VBUK-GBSTK (Overall processing status of document).
regards,
srinivas
*reward for useful answers*

How to Archive PO for which delivery costs has not been settled ?

Hi dear experts,
For Intra company STO, documents weren't getting archived due to the error message.Scenario is mentioned below.
During pretreatment of MM_EKKO archiving object (TA: SARA), I get an amazing huge amount of PO position which can not be archived due to "*Delivery costs have not been cleared*".
I tried several ways to find out how to solve this issue but without any success.
Point is that we do not clear delivery cost regarding those PO positions.
It means that those PO's won't never be cleared.
Any ideas about how I can fix this issue?
Best regards,
Deepak

Dear Jurgen,
Scenario is as follows:
An Intra company STO is created without delivery costs.
Next step is delivery creation.
Shipment is created with creation of shipment cost document
The shipment costs are distributed accordingly to the items in the PO and they're stamped back in the PO with the condition type ZFRB(copy of FRB1)
This will act as a reference and added to the material cost in the receiving plant.
As the shipment cost document creates a service PO and its cleared with a Invoice being posted in MIRO and subsequently in FI,they aren't clearing the value which is open in the Original stock transport order.
Regards,
Deepak

Delivery archived

Similar Messages

Maybe you are looking for