Sync Project Documentation with General Documentation

Hi Experts,
We are trying to utilize SolMan 7.1 for the documentation and configuration
We are following release approach for the implementation and as soon as Release 1 finish testing we will start Release 2. Now for this approach we decided below option in SolMan
1) Create Template project for all processes and documentation
2) Crate Implementation project for each release from Template Project. Copy all documents from the General Documentation tab to Project Documentation. During the release-1 we are going to update the documents in Project documentation tab.
a) Now question is how we going to sync all these updated document from Project Documentation to General Documentation?
b) Is there any standard way to check what are the differences between the document in General Doc and Project Doc tab?
SA_PROJECT_UPDATE only checks what are new documents available in Project Documentation tab. It doesn't tell if the same document is updated in Project Tab.
Anyone has any other approach to handle this kind of situation please let me know your thoughts.
Thanks in advance!
Thanks,
Shaun
Edited by: shaun99 on Jan 25, 2012 8:20 PM

I think I have now found the answer to my own question.
From Enterprise edition 7.0 the change manager can link directly to process information, such as implementation documentation, test case etc.
If you want to refer to documents within the CR you can use all documents already stored in the knowledge warehouse.
it seems that this is available through the "Customer Fields" tab in "transaction data" of a change request.

Similar Messages

Syncing project tasks with Task lists

Hi,
I am syncing tasks from microsoft project file to SharePoint tasks list. However, there is a possibility that my project file will exceed more than 1000 tasks over time and one of the limitation with SharePoint & Project syncing is that the project file
that am syncing with SharePoint can't exceed more than 1000 tasks. Microsoft says that I need to use a brand new project file to sync the 1000+ tasks but what about the dependencies? say for eg: For task 1001, if I have a dependency on task 1000, do I
have to set up the dependencies in SharePoint?
Please help,
techie

Hi,
A fact you might need to consider is that there will be possible severe performance issues with 1000 tasks in a list, plus with the extra task dependencies.
To deal with large number of tasks when syncing between Project and SharePoint Task list, it is recommended that “750 is about as large as you would want to go with
a project plan. A SharePoint List should be even smaller for best functionality and usability, 100 tasks in a SharePoint task list is a reasonable number to work with”:
https://support.microsoft.com/en-us/kb/2876901?wa=wsignin1.0
Thanks
Patrick Liang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Project documentation with ChaRM

We have a lot of project documentation from our implementation - this includes functional and technical specificatons.
When we enter our maintenance cycle I want to make sure that this documentation is kept up to date.
If, for example, there is a change request for an alteration to a report. I would like that the original functional and technical specifications could be linked to that change request for them to be updated. So that the change manager can see that there is documentation completed before confirming the change request & also that our implementation documentation is kept up to date.
Is this a possibility?

I think I have now found the answer to my own question.
From Enterprise edition 7.0 the change manager can link directly to process information, such as implementation documentation, test case etc.
If you want to refer to documents within the CR you can use all documents already stored in the knowledge warehouse.
it seems that this is available through the "Customer Fields" tab in "transaction data" of a change request.

Report on project documentation in Solotion Manager

Hello,
I want to know if exists a report or a query to display object linked to project documentation.
I tried with SOLAR_EVAl, but the result is not good.
Can someone help me?
Regards
Anna Maria

Hi
goto solar_eval
businees blueprint->Assignements->documents & Links
give ur project name and press execute
the list will be displayed with all the document naem in the left panel as per the scenario and for linked documents it wil be under the column Name(Links) on the right side with other info like userid etc.
If your requirement is much more than this than u need to go for development.
Regards
Prakhar

Project documentation through solution manager -reg

Hi,
We would like to do project documentation through solution manager
we work on solution manager 2007 with ehp 1
what ever projects we handle like packing for exports etc.. we would like to create them as projects in solution manager and maintain the documentation
request some one to provide step by step guide for the same
regards,
Madhu Kiran

Hi
HAve u seen this
https://websmp210.sap-ag.de/~sapdownload/011000358700002006042008E/HowTo_Impl_Bus_Proc.pdf
in addition for manual just simply write in Structure tab to create ur folder
Hope it solves ur prb
Regards
Prakhar

Transporting SPRO img project documentation

Hi,
We have a system config client copied from another system.
We currently have a requirement to transport all SAP SPRO project documentation from source system to another without a system export.
We were able to transport the project with the meta data and have the configuration.We now require the related sapscript notes that relates to the specific IMG configuration settings.
Please can you advise how to get this documentation over to the new system?
Kind Regards

Hi,
Please check the below link it might help you :
http://help.sap.com/erp2005_ehp_04/helpdata/EN/81/8c5738ee806b0ee10000009b38f889/frameset.htm
Regards
Sreedhar Reddy

Signal express project documentation

I've been having problems with the "project documentation" section of my Sound And Vibration Assistant (based on signal express). It's been locking up and corrupting previously good projects. When I add the peak search step to the documentation and hit "view as - cascade" everything seems to fail, the project locks up, is not responding, it doesn't even let it close, have to call task manager to close it, after that when I try to open again that same project, it doesn't even open fully and is locked up again. Any help with this would be apreciated.

Hello Seth, I'm attaching a couple of files. The first one contains a screen shot of the steps that I'm using in the project, The second one is the message that I received when SAV assistant quit on me and the third one is the printout of project documentation before it started failing, the second to last graph is the one I think is creating most of the problems, when I removed that graph from project doc it worked fine, other than when I tried to resize one of the other graphs.
I'm gathering data from an accelerometer I take the time domain signal and transfer it to freq domain, zoom in on the power spectrum linear magnitude scale.
Let me know if you need any other info.
F@SII
Attachments:
SAVsteps.docx ‏200 KB
SCREEN SHOT FAILURE LABView.docx ‏213 KB
hppscan6.pdf ‏233 KB

BW project documentation format

Hi,
Can anyone send me a format for BW project documentation. my email id is :
[email protected]
Thanks in advance..

Hi,
Following document is the sample BI PROJECT BLUEPRINT Documentation realted to
FI Module.
    BI Project
   ASAP Business Blueprint
   Accounts Receivable
BI TEAM
     ASAP Business Blueprint
FI-Accounts Receivable
     Project Mission Excellence
Created by               : BI Team
Date of creation               : 28.02.2007
Changed by               :
Date of the last changes     :
Version                    : BW 3.53 V
Sign Off Date     Signature Customer     Signature Consultant
BW: Accounts Receivable Analysis
FIAR LINE ITEM (Info Cube)
This enables you to analyze accounts receivable data from SAP R/3.
Info Cubes Used
     Accounts Receivable: Line Items (technical name FI_AR_C03
Key Points
     Analysis of accounts receivable line items
     Analysis of the payment history (payment volume and days in arrears) of customers per company code and fiscal year period
FI_AR_C03
This Info Cube enables you to view information about accounts receivable line items from R/3 such as:
     Dealer wise/Customer wise monthly collection /cheque returns/Net Collection
     Sales officer wise monthly collection
     Branch wise collection
     Net Collection Report.
     Book Debt Summary.
Data flow for Cube 0FIAR_C03 ( FI AR Line Items )
FIAR LINE ITEM (ODS)
1 Scope
Technical Name: FI_AR_C03
This Info Cube contains all the Accounts Receivable line items that will be loaded from the R/3 system.
2 Expectations / Requirements:
All Collection related reports based on different parameters for e.g.: Day, month, Business Area, Posting Date will be built upon this cube.
3 Data Modeling
Characteristics     Technical Name     Approx. No
Of Records     Enhancement     Dimension
Company Code      0COMP_CODE                Company Code
G/L Account      0GL_ACCOUNT                G/L Account
Credit Control Area      0C_CTR_AREA                Customer
Special G/L indicator      0SP_GL_IND                Document Data
Baseline date for due date calculation      0BLINE_DATE                Due Dates
Payment method      0PYMT_METH                Payment Data
Payment block key      0PMNT_BLOCK                Payment Data
Terms of payment key      0PMNTTRMS                Payment Data
Chart of accounts      0CHRT_ACCTS                G/L Account
Account type      0ACCT_TYPE                G/L Account
Country key      0COUNTRY                Payment Data
Customer number      0DEBITOR                Customer
Item Status      0FI_DOCSTAT                Document Status
Account Number of the Branch      0FI_SUBSID                Dunning Data
Posting date in the document      0PSTNG_DATE                Document Data
Clearing date      0CLEAR_DATE                Payment Data
Document type      0AC_DOC_TYP                Document Data
Document Date      0DOC_DATE                Document Data
Posting key      0POST_KEY                Document Data
Dunning area      0DUNN_AREA                Dunning Data
Date of last dunning notice      0LAST_DUNN                Dunning Data
Dunning block      0DUNN_BLOCK                Dunning Data
Dunning level      0DUNN_LEVEL                Dunning Data
Dunning key      0DUNN_KEY                Dunning Data
Due date for net payment      0NETDUEDATE                Due Dates
Reason code for payments      0REASON_CDE                Due Dates
Business Area      0BUS_AREA          Enhancement     Product
Fiscal year / period      0FISCPER                Time
Fiscal year variant      0FISCVARNT                Time
Fiscal Year      0FISCYEAR               Time
Division     0DIVISION          Enhancement     Product
Employee     0EMPLOYEE          Enhancement     Sales Area
Sales Office     0SALES_OFF          Enhancement     Sales Area
Cycle Wise Week     V_CYCWEEK          Enhancement     Document Data
               Dimension     Approx. Entries     Line Item
Company Code
Customer
Payment Data
Due Dates
G/L Account
Document Data
Sales Area
Dunning Data
       Data Sources Involved     App. Comp.
0FI_AR_4     FI-AR
0FI_SUBSID_TEXT     FI-IO
0GL_ACCOUNT_TEXT     FI-IO
0PMNTTRMS_TEXT     FI-IO
0PMNT_BLOCK_TEXT     FI-IO
0PYMT_METH_TEXT     FI-IO
0ACCT_TYPE_ATTR     FI-IO
0CHRT_ACCTS_ATTR     FI-IO
0COMP_CODE_ATTR     FI-IO
0C_CTR_AREA_ATTR     FI-AR-IO
0GL_ACCOUNT_ATTR     FI-IO
0PMNT_BLOCK_ATTR     FI-IO
0PYMT_METH_ATTR     FI-IO
0SP_GL_IND_ATTR     FI-IO
0ACCT_TYPE_TEXT     FI-IO
0AC_DOC_TYP_TEXT     FI-IO
0CHRT_ACCTS_TEXT     FI-IO
0COMP_CODE_TEXT     FI-IO
0COUNTRY_TEXT     SAP-R/3-IO
0REASON_CDE_TEXT     FI-IO
0SP_GL_IND_TEXT     FI-IO
0C_CTR_AREA_TEXT     FI-AR-IO
0CUSTOMER_ATTR     LO-IO
0CUSTOMER_TEXT     LO-IO
Navigation Attributes
0COMPANY     Company
0BAL_FLAG     Indicator: G/L Account is Balance Sheet Account
0INCST_FLAG     Indicator: G/L Account is P&L Account
0SEM_POSIT     Planning Item
0BPARTNER     Business Partner
0COUNTRY     Country key
0INDUSTRY     Industry sector
0SALES_OFF__0COUNTRY     Country
0SALES_OFF__0REGION     Region
0SALES_OFF__0SALES_DIST     Sales District
                                                                        KEY FIGURES
                              Description      Technical Name                       Unit
Amount in Local Currency with +/- Signs     0DEB_CRE_LC     0LOC_CURRCY
Cash discount amount in local currency     0DSC_AMT_LC     0LOC_CURRCY
Foreign currency amount with signs (+/-)     0DEB_CRE_DC     0DOC_CURRCY
Cash discount amount in document currency     0DSC_AMT_DC     0DOC_CURRCY
Credit amount in foreign currency     0CREDIT_DC     0DOC_CURRCY
Credit amount in local currency     0CREDIT_LC     0LOC_CURRCY
Debit amount in foreign currency     0DEBIT_DC     0DOC_CURRCY
Debit amount in local currency     0DEBIT_LC     0LOC_CURRCY
Cycle Wise Balances     V_CYCBAL     Currency
4 Data Loading Strategy (Frequency, event chain)
Data will be loaded daily in this cube using suitable process chains.
5 Transfer rules
Standard Business Content Transfer rules will be enhanced with Business Area, Cycle Week and Employee.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be enhanced with Business Area and Division.
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
If required suitable aggregates will be created after going live according to BW statistics proposals.
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area, Division, Employee and Cycle Week are not present in the standard cube. The cube will be enhanced with the above-mentioned characteristics and to derive the values of the same the exit RSAP0001 will be used to enhance the data source 0FI_AR_4.
Sales Employee: Check return or reversal get original document based on check number and find sales employee for original document.
Cycle Week: derived cycle week from Period. For cycle wise reporting.
Document Type: DU & DZ hard coded for Collection and BB & BE hard coded for Check Return.
Fiscal year variant: Fiscal year Variant W2 is hard coded for Company Cycle.
10 Assumptions / Prerequisites
11 Authorization and User Roles
Company Code, Branch/Sales Office, Division.
     FIAR LINE ITEMS ODS
1 Scope
Technical name: 0FI_AR_O03
2 Expectations / Requirements:
3 Data Modeling
List of Objects in the ODS are same as in FIAR Line Items Cube.
Following Objects are taken, as Key Fields and rest all are Data Fields.
1. Company Code
2. Customer Number
3. Fiscal Year
4. Fiscal Year Variant
5. Accounting Document Number
6. Number of Line Item within Accounting Number
7. Due Date Item Number
8. Cycle Week
4 Data Loading Strategy (Frequency, event chain)
Data will be loaded daily to this ODS using suitable process chains.
5 Transfer rules
Standard Business Content Transfer rules will be used.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be used
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
Not Applicable
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area, Employee and cycle week are not present in the standard ODS. The ODS will be enhanced with the above-mentioned characteristics and to derive the values of the same the exit RSAP0001 will be used to enhance the data source 0FI_AR_3.
10 Assumptions / Prerequisites
11 Authorization and User Roles
FIAR Transaction Data
Data Flow for Cube OFI_AR_C02
1 Scope
Technical name: 0FIAR_C02
This Info Cube contains all accounts receivable data (transaction figures) that was downloaded from the connected source system(s).
2 Expectations / Requirements:
This Cube enables to calculate dealer wise net collection by calculating collection and cheque return. Here you can analyze collection value, cheque return value and net collection value. The net collection value is derived after subtracting cheque return value from the collection value.
3 Data Modeling
CHARACTERISTICS
Characteristic     Technical Name     Approx No Of Records     Enhancement     Dimension
Company code           0COMP_CODE                 Company Code
Currency Type           0CURTYPE                 Currency Type
Customer number           0DEBITOR                 Customer
Fiscal year      0FISCYEAR                Time
Fiscal year / period      0FISCPER                Time
Fiscal year variant      0FISCVARNT                Time
Posting period      0FISCPER3                Time
Business Area     0BUS_AREA          Enhancement     Business Area
Profit Center     0PROFIT_CTR          Enhancement     Profit Center
Dimension     Approx. Entries     Line Item
Customer
Company Code
Currency Type
Data Sources Involved     App. Comp.
0FI_AR_6     FI-AR
0COMP_CODE_ATTR      FI-IO
0COMP_CODE_TEXT     FI-IO
0CUSTOMER_ATTR     LO-IO
0CUSTOMER_TEXT     LO-IO
0PROFIT_CTR_ATTR     FI-IO
0PROFIT_CTR_TEXT     FI-IO
0BUS_AREA_ATTR     EC-PCA-IO
0BUS_AREA_ TEXT     EC-PCA-IO
Navigation Attributes
0DEBITOR__0BPARTNER     Business Partner
0DEBITOR__0COUNTRY     Country key
0DEBITOR__0INDUSTRY     Industry sector
0COMP_CODE__0COMPANY     Company
KEY FIGURES
Description     Technical Name     Unit     Enhancement
Accumulated balance     0BALANCE     0LOC_CURRCY
Sales for the Period      0SALES      0LOC_CURRCY
Total credit postings     0CREDIT      0LOC_CURRCY
Total Debit Postings     0DEBIT     0LOC_CURRCY
4 Data Loading Strategy (Frequency, event chain)
The data will be loaded weekly.
5 Transfer rules
Standard Business Content Transfer rules will be enhanced with profit center and Business Area.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be enhanced with profit center and Business Area.
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
Suitable aggregates if required will be created according to BW statistics proposals.
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area and Profit Center are not present in the standard cube. The cube will be enhanced with the above-mentioned characteristics and to derive the values of the same. The exit will be used to enhance the data source 0FI_AR_6.
10 Assumptions / Prerequisites
11 Authorization and User Roles
Thanks,
Sankar M

Pilot project documentation

hi folks-
can anybody give me the details of any pilot project documentation details

need some help for creating project documentation.What do you need help with? Your post is quite useless in finding that out as it is now.

Project documentation tab - cannot access own templates

We are using SM4.0. In the project template I have created new document types and assigned templates to the document types. When using these to create docuements in the Blueprint Project Documentation tab, the templates are not defaulted, we just get a blank Word document.
The template are defautled for the standard SAP documents.
Any ideas why we are unable to use our custom documents with templates?

Thomas...
It should reflect in project documentation tab ...but some times it will not ...i had a same problem for couple of documentation templates...
The work around is ...once you create document type before saving attach the document template and then save it. instead of creating the document type + save +attach document template.
Hope this helps you,
Praveen

Status for project documentation

Hi Experts
Just wanted to check u2026
If there are 10 status for project documentation defined in the system out of which only 5 are applicable for my project and hence I want to hide( not just make it gray u2013 I know this I can manage using restriction @ S_IWB_ATTR )..
How and where I can configure this only for my project and not for entire system ? .
Cheers
Aditya

Hi
Simply create a documentation type and assign a status schema to it with required set of status values in the schema
moreover if you make the Check on Global Indicator in the Project Documentation Template where you assign schema to your documentation type their if do the Check it is available to all but if you dont make the check it is available for your project only so
you have to assign it after creating from Unused Documentation types to your project documentation type library
so steps will be
create a documentation status schema via spro
goto project in solar_project_admin and here create the doc type
assign the doc type with new status schema .......also dont make the check for global
save and return to project screen and here assign the doc type from unused zone to your available proj doc types
Hope it solves
Regards
Prakhar
Edited by: Prakhar Saxena on Aug 13, 2011 6:38 PM

Error --while uploading document in solar01 Project documentation

Dears,
We have created a imp project in solman and I have full authorization of solar01,solar02,solar_project_admin.Now when I go to project documentation->Add document and click on upload documement, It gives error:
"No authorization to upload document."
Please suggest.
Shivam

Hi,
chk ur authorizaion errors... su53 dump.
Thx,
waseem

Project Documentation Format

Hi SAPians,
We are a bunch of SAP trainees, and have recently completed a corporate training as a final year project.
We need to prepare documentation, report and presentation for project completion and degree.
we have all the screen shots, theory explanation about SAP and our related project, but we're not able to add them up.
Please provide us a template idea of what should be the contents of a project documentation should be, or if you could provide us info on how should the index looks like, that would be a great help.
Thanks

SAP's tool for creating documentation is [Knowledge Warehouse|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/8f/d82d37ba466b5be10000009b38f936/frameset.htm].
Hope this helps,
Rossen

Project Documentation tab: can you 'freeze' a graph so another can be added and compared against?

I've been using the Project Documentation view recently to quickly compare dc signals against changes that I make to an electrical system. What I'm trying to do is capture a few seconds of a DC signal, stop acquisition, make a change in the system, then capture a few more seconds of the same signal and compare the two.
Project Documentation view is nice because I can drag the graphs onto the document for quick on the fly comparison.
Problem is, I drag a acquired signal's graph onto the document expecting the waveform to 'freeze' so that I can capture another segment of data and drag that graph onto the document for comparison. But once I acquire this second burst of data the first graph captures the live waveform, overwriting the baseline waveform I'm trying to compare against.
Is there a way to screencapture or freeze the graph so that multiple graphs can be stacked within the document form without them all updating?
SCXI- 1000 Chassis w/ 1346 adapter
PCI 6281 DAQ card
SCXI- 1520 Bridge Board w/ 1314 Terminal Block (x2)
SCXI- 1180 Feedthrough Panel w/ 1302 Block
Signal Express 2014.
Win7 Enterprise

Hi OKors,
I’m not sure if you can do exactly what you want. If it were me, I would take the first reading, then save it to an LVM file, then take the second reading, store that to an LVM file, then load the files to compare.
TimC
National Instruments
Applications Engineer

Project documentation

Hello,
We hare using solution manager for project documentation. We have put a lot of documentation into various projects.
Is there a central transaction on the solution manager, where we can see all documentation stored, in the different documentation classes?
Thanks in advance

Hi,
try SOLAR_EVAL transaction - go to Analysis -> Project -> Configuration -> Assignments -> Documentation -> and specify Projects you would like to browse.
Or try SIIALL0 transaction for Knowledge Warehouse browsing.
Hope this helps, Marek

Sync Project Documentation with General Documentation

Similar Messages

Maybe you are looking for