Q&A DB,BPML,Blueprint,scope document FOR PS PROJECTS

Hi,
If any body have Q&A DB,BPML,Blueprint,scope document FOR various types of  PS PROJECTS ,please send me at [email protected]
Thanks]
Muzamil

You can use the -replace operator and a regex to do this.
'<692>) Tj ET' -replace '\s*<(\d+)>.+','$1'
692
In your code, you should be able to use that when you set $value:
$Value = $line[1] -replace '\s*<(\d+)>.+','$1'
The $1 is a "backreference", which designates the first capture group (inside the parens) in the regex.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Similar Messages

  • How to find posted documents for Master Data in BW?

    Hello,
    We are planning to use Knowledge Warehouse to store some documents against some Master Data like 0PROJECT. The idea is to use those documents when reporting on real cost versus budget.
    We created a custom interface that we use to create new master data in BW directly, and we have an input field which precises the name of the files to be loaded. That works fine.
    However, we need now to include in that custom interface a table which will display the existing documents for the project currently displayed. We want to avoid to load a same document twice.
    I do not succeed in linking the master data values and the documents. I found the table RSODPHIOMA. It contains the key of the documents that I look for. How can I make the link between that key and my master data values?
    Regards
    Laurent

    Hi
    go to RSA1 -> Infosources ->
    Here go to top screen ...or find the control icon thru cntl +F
    here enter your infosource/infoobject name......
    Double click on the result and it will show the infosource...under that infopackage
    Assign points if useful
    Regards
    N Ganesh

  • Design consideration document for HCM

    Hi guru,
    Greetings for the day,
    I facing a problem here in creation of “design consideration” document for the HCM project, where any one can help me out by sending a sample HCM design consideration  document for my project.
    Thanks in advance for you reply.
    You can send the document to my mail id of     babusaphr @ gmail.com
    Regards,
    Babu.A

    Hi..
    It is Client Specific..

  • Blueprint Document for KM

    Hi All,
    I am looking for a template of a blueprint document for a SAP KM implementation.
    If anyone has a template pls email it to me, (if the blueprint document has the sectons filled in , all the more great), or if you can redirect me to a URL where I can find the revlevant information, it will be very helpfull.
    Thanks in advance.
    Will definitely reward points.
    Regards,
    Vivek

    Hi Vivek,
    The only document that comes to mind are the ones in the Portal Roadmap that can be found at https://websmp203.sap-ag.de/roadmaps.
    Regards
    Paul Chambers

  • Can anyone please provide me Blueprint Document for BW

    Can anyone please provide me Blueprint Document for BW on <removed>.I will be very thankful to u,,,and <soliciting points for answers is forbidden >....
    Edited by: Arun Varadarajan on Nov 27, 2008 3:00 PM

    please search the forums for the same - the necessary links have been given in previous posts and blueprint is something that has been discussed many a time on the forums...
    Arun
    Locking the post.....

  • Creating an Architecture Document For a Portal

    I have been asked to come up with an Architecture Document for a public facing SharePoint 2010 site.  I am familiar with the SharePoint 2010 technologies, however I need a starting point on where and how to start the Architecture document.  Is there any Architecture Template Document that exists so that I can use them?

    Hi
    I cannot share the full and final doc with you but following Index will help you creating the Architecture document from the scratch
    1     Document Overview............................................................................................................ 7
    1.1     Scope............................................................................................................................... 7
    1.2     Audience......................................................................................................................... 7
    2     Logical Architecture............................................................................................................ 9
    2.1     Overview.......................................................................................................................... 9
    2.2     Diagram........................................................................................................................... 9
    2.3     Component Description.............................................................................................. 9
    3     Physical Architecture....................................................................................................... 11
    3.1     Overview....................................................................................................................... 11
    3.2     Production Environment.......................................................................................... 11
    3.2.1     Diagram................................................................................................................... 11
    3.2.2     Component Description....................................................................................... 12
    3.2.3     Hardware Requirements...................................................................................... 14
    3.2.4     Software Requirements........................................................................................ 14
    3.3     Staging Environment................................................................................................. 14
    3.3.1     Diagram................................................................................................................... 15
    3.3.2     Component Description....................................................................................... 15
    3.3.3     Hardware Requirements...................................................................................... 15
    3.3.4     Software Requirements........................................................................................ 16
    3.4     Development & Test Environment......................................................................... 16
    3.4.2     Diagram................................................................................................................... 16
    3.4.3     Component Description....................................................................................... 17
    3.4.4     Hardware Requirements...................................................................................... 17
    3.4.5     Software Requirements........................................................................................ 18
    4     Non-Functional Requirements....................................................................................... 19
    4.1     Security......................................................................................................................... 19
    4.1.1     Requirements......................................................................................................... 19
    4.1.2     Authentication........................................................................................................ 19
    4.1.3     Authorization.......................................................................................................... 19
    4.2     Availability..................................................................................................................... 21
    4.2.1     Requirements......................................................................................................... 21
    4.2.2     Hardware Redundancy and Failover................................................................. 22
    4.2.3     Scaling Logical SharePoint Components......................................................... 22
    4.2.4     Disaster Recovery.................................................................................................. 22
    4.3     Performance................................................................................................................. 23
    4.3.1     Requirements......................................................................................................... 23
    4.3.2     Performance & Capacity Expectations.............................................................. 23
    4.3.3     Size and Volume Assumptions.......................................................................... 23
    4.3.4     Performance Testing Approach.......................................................................... 25
    4.3.5     Performance Tuning Approach.......................................................................... 25
    4.3.6     Monitoring and Reporting.................................................................................... 26
    4.4     Accessibility................................................................................................................. 26
    4.4.1     Requirements......................................................................................................... 26
    4.4.2     Internal Access....................................................................................................... 26
    4.4.3     Remote Access...................................................................................................... 26
    4.5     Auditing & Reporting................................................................................................. 27
    4.5.1     Requirements......................................................................................................... 27
    4.5.2     Approach................................................................................................................. 27
    4.5.3     Audit Reports.......................................................................................................... 27
    4.5.4     Diagnostic Logging............................................................................................... 28
    4.5.5     Portal Usage Reporting........................................................................................ 28
    4.6     Exception Handling & Logging............................................................................... 28
    4.6.1     Exception Handling............................................................................................... 28
           Application..................................................................................................................... 29
    4.6.2     Logging.................................................................................................................... 29
    4.7     Caching......................................................................................................................... 29
    4.7.1     Disk based caching for BLOBs........................................................................... 29
    4.7.2     Client-side caching............................................................................................... 30
    4.7.3     Object Caching...................................................................................................... 30
    4.8     Maintainability.............................................................................................................. 31
    4.8.1     Backup and Restore.............................................................................................. 31
    4.8.2     Archiving & Purging.............................................................................................. 32
    4.9     Regional Deployment................................................................................................ 32
    4.9.1     Conceptual Diagram............................................................................................. 32
    4.9.2     Feature Summary.................................................................................................. 33
    4.10      Service Management.............................................................................................. 35
    5     Search Architecture.......................................................................................................... 36
    5.1     Introduction.................................................................................................................. 36
    5.2     Key Design Considerations..................................................................................... 37
    5.2.1     Distributed Geographical Deployment............................................................... 37
    5.2.2     Content Sources.................................................................................................... 37
    5.2.3     Availability & Performance................................................................................... 37
    5.2.4     Physical Infrastructure.......................................................................................... 38
    5.2.5     Search as a Shared Service................................................................................ 38
    5.3     Search Architecture in portal..................................................................................... 38
    6     Content Deployment Architecture................................................................................ 41
    6.1     Introduction.................................................................................................................. 41
    6.2     Key Design Considerations..................................................................................... 41
    6.2.1     Distributed Geographical Deployment............................................................... 41
    6.2.2     Security.................................................................................................................... 42
    6.2.3     Availability............................................................................................................... 42
    6.2.4     Publishing Frequency.......................................................................................... 42
    6.2.5     Physical Infrastructure.......................................................................................... 42
    6.2.6     User Contributed Content.................................................................................... 42
    6.3     Content Deployment in portal................................................................................... 43
    7     References.......................................................................................................................... 45
    8     Key Decisions.................................................................................................................... 46
    9     Dependencies.................................................................................................................... 47
    10      Key Contacts................................................................................................................... 48
    11      Appendix A – Active Directory Requirements........................................................ 49
    12      Appendix B – Capacity Sizing Model........................................................................ 51
    13      Appendix C – Hardware & Software Requirement Summary............................. 53
    14      Appendix D – Site Architecture................................................................................... 55
    Regards
    Deepak Aggarwal

  • Generate accounting document for cancel of credit memo

    Hii Guy,
    Need your help to solve this problem.
    My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
    my user cannot perform creating of accounting document for this cance of credit memo. what are the tcode to generate accounting document ?

    Nizamkz wrote:Hi,
    >
    > Hii Guy,
    >
    > Need your help to solve this problem.
    >
    > My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
    Are you sure its VK11???? I guess for the cancellation if billing document its VF11......
    Try to do the manual release to accounitng....by going to VF02 and pressing the Green Flag button after entering the cancellation document number. Or Else Try to reverse the posting with FB08.
    Thanks,
    Raja

  • Need Single Billing Document for Materials and Services in Sales Order

    Hello Friends,
    I am selling FERT items and DIEN items in the Sales Order.
    Document flow as follows:
    Finished goods - Order-Delivery-Billing
    Services - Order-Billing
    In this process 2 seperate billing documents are created
    i.  Delivery Related Billing document for Finished goods.
    ii. Order related Billing document for services.
    I want to create a single billing document for both the items (FG & Services) in the sales order.
    Please suggest.
    Thnx.

    Sorry for the delay friends.
    Somebody suggested me to make services 'relevant for delivery' to ensure single billing document.
    What I did were the following steps:
    1. Copy Item Category TAD to ZTAD and make is 'relevant foir delivery'
    2. Assign Item Category ZTAD to Sales Order type and Item Cat Group 'LEIS'
    3. Go to Deliveries Item Categories and through new Entries add ZTAD. Make ZTAD relevant for Picking.
    4. Go to copy control 'Order to Delivery' and insert ZTAD in Item Categories relevant for this combination.
    Now when I create sales order with materials and services, they pass over to the delivery document and in the Services item, storage location/plant is greyed out. Only the picking quantity is required to be filled.
    PROBLEM :
    I am not getting the price of Services item in the billing document.
    Billing document copies all line items (tangible and intangible) from Delivery Document
    It takes the services item details/quantities etc. to VF01 but the price comes '00.00'
    Any suggestions.
    Is this legally viable? Someone told me its not legally correct.
    Thanks.
    Mohammed

  • Table to look for change documents for users

    Hi friends,
    Is there any standard table to look for change documents for a user?change document through SUIM does not give the correct log.
    Thanks for you support.

    Julius
    Looking at another of Tracy's other post (http://scn.sap.com/thread/3598947) she's trying to use ACL. Hence needing to know the tables to write joins/queries to hit tables within ACL
    I've seen ACL used and have had the fun experience of Auditors using Google to find tables to perform checks on without context of what has actually been implemented in their particular system.
    Regards
    Colleen

  • Delivery Document for Services

    Hello Experts,
    I have a scenario which I am looking for an SAP solution. My client provides consultancy services and bills customers for it. At the beginning of the contract, customer gives a letter of intent (LOI) which authorised commencement of work. After work is completed, the customers signs a job completion form/service entry sheet, which is the basis on which the client can invoice the customer for the hours/days spent. Thinking along OTC, it looks to me that the  LOI could represent a sales order, but I am looking for a document to represent the job completion form/service entry sheet. Can we have a delivery document for services? Is there any other document that can perform the same function as delivery in this scenario? I think there has to be another document after the sales order that will represent the actual hours/days spent on the job which the invoice can reference in billing the client.
    Thanks for your prompt help.
    Luqman

    Its part of Customer Service. And widely know as After Market.
    Is very much integrated with SD as well as PS.
    DP90 csan be used by PS & SD both.
    Whereas, if your refer DP90, its purely based on Sales Document.
    Refer following SAP Help link for reference/understanding:
    - [ Resource-Related Billing |http://help.sap.com/saphelp_dimp50/helpdata/en/59/54fc37004d0a1ee10000009b38f8cf/content.htm|also CS billing process]
    Also refer, SAP Note 301117 - Enhanced documentation for dynamic item processor (DIP).
    As DIP profile(TCode ODP1) is the critical part of RRB configuration.
    Regards
    JP

  • Accounting document for Export Excise invoice

    Dear All,
    We have two scenario's one is Domestic Sales & Export Sale.
    In domestic sales as per the normal flow of document we create excise invoice after billing document and accounting documents are also generated and updated in the billing document accounting (VF02). Accounting document for excise invoice has been generated.
    However in export sales we create excise invoice with the reference of billing document but no accounting document has been generated for excise invoice.
    Can u please tell me where i have to make changes so my accounting document for export excise invoice will generate?
    Thanks & Regards,
    Ratish

    Hi ALL,
    There are 4 export scenario :
    1) Deemed export 2) Export under Bond 3) Export under claim for rebate [No bond] 4) Export under Letter of Undertaking.
    3) In export under no bond process is :- we pay the excise on the goods for exports and create the ARE-1 doc and send to port where the customers officials note the actual quantity of goods on the ARE-1 doc and stamped it. Then these stamped ARE-1 will be send to the excise range of the despatch plant(for exports) where we claim the rebate.
    Now if you are not able to generate the accounting doc for such a scenario some of the consultants may suggest u to use the user exit (J_1I7_USEREXIT_DUTY_IN_EXPORT) and pass the the value X to the parameter SUPPRESS_CALCULATION this intern will help u to generate the Accounting doc also. but real problem lies somewhere else.
    Actual Solution: Maintain J1ID (Customer excise details)
    for export customer maintained the excise indicator to 3 {Nil Duty} insted of 1 {100% tax}.
    Problem will be solved
    Regards
    Satish Zade

  • Single billing document for multiple delivery documents

    Hi,
    Can someone tell me how to configure or proceed to make single billing document for multiple delivery documents.
    Document flow: Contract--> Order---> Delivery----> Billing
    -Thanks

    Being an old member of the forum, there is no need to stress the importance of adhering to forum rules where it has been clearly spelled out to avoid posting repeated queries.
    If you search the forum or Google it, you will find lot of documentations available on the same topic.  Take the inputs and try on your own.  Still if you face any issue, update here.
    G. Lakshmipathi

  • Configuration documents for Training and event management &apprisals?

    hello xperts
    can anyone forward me configuration documents for treaining and event management and apprisal? to [email protected]

    Thanks for your suggestions.
    i can't go through new appraisal model with catalog & template, because client is not having ESS,MSS.  appraisal has to done in the ECC only.
    Done the customization like this :
    created scales
    created appraisal model and assign the scales
    for appraisal, Employee can do from APPCREATE transaction rate his own ratings and save.
    Now Appraiser (Manager) from APPCHANGE complete the appraisal.
    now my requirement is (1) after saving the APPCREATE by the employee, notification has to go to his reporting manager only. (2) Manager can do review/change and complete the process to his Employees only (who are reporting to him)
    how can i do this, standard functionality is there or i have to go for ABAP coding ? if ABAP coding what i have to ask them to do.
    Please help in this requirement.
    Thanks and Best Regards,
    Praneeth kumar

  • LSMW me51n, how to create one PR document for all the records in the  file

    HI all,
    I need to create LSMW for t-code me51n -Create Purchase Requisition. I`m using Bapi BUS2105, method CREATEFROMDATA, idoc message type PREQCR, basic type PREQCR03. The problem is that the LSMW is creating different idoc and different PR document for every record in the source file. My requirement is to create one PR document for one source file (Every source file is different Purchase Requisition) . I`m trying to do this with writing some code(global functions ) in the 'Mapping and conversion rules'  events - BEGINOF_TRANSACTION_, ENDOF_TRANSACTION__..., but i`m not very sure what exactly i`m doing .
    Please help me resolve this problem, any help will be appreciated .
    Best regards, Emil Milchev.

    Thank you for you answer.
    But I have found faster way of doing it - two source structures, one HEADER and ONE ITEM.
    HEADER: one empty text field and identificator for it.
    ITEM: everything else.
    Then everything was just fine, i`ve mapped the different IDOC segments by PREQ_ITEM fields (equal values in the source file : 10-10-10..., 20-20-20,.... etc.) and put all required fields for my LSMW
    SOURCE FIELDS:
    Z_ME51N_V2 - MASS_UPLOAD - CREATE create
    Source Fields
    UPFILE                    upload file
                IDENT                          C(010)    ident
                                               Identifing Field Content: header
                TEXT                           C(001)
                UPFILE2                   123
                    IDENT                          C(010)    ident
                                                   Identifing Field Content: item
                    BSART                          C(004)    Document type
                    BANFN                          C(010)    Purchase requisition number
                    BNFPO_FOR_MAP                  N(005)    Item number of purchase req. for MAPPING acc.
                    BNFPO                          N(005)    Item number of purchase requisition
                    KNTTP                          C(001)    Account assignment category
                    PSTYP                          C(001)    Item category in purchasing document
                    MATNR                          C(018)    Material Number
                    WERKS                          C(004)    Plant
                    LGORT                          C(004)    Storage Location
                    MENGE                          N(013)    Purchase requisition quantity
                    EKGRP                          C(003)    Purchasing group
                    KONNR                          C(010)    Number of principal purchase agreement
                    KTPNR                          N(005)    Item number of principal purchase agreement
                    LIFNR                          C(010)    Desired Vendor
                    FLIEF                          C(010)    Fixed Vendor
                    AFNAM                          C(012)    Name of requisitioner/requester
                    PREIS                          AMT4(011) Price in purchase requisition
                    ABLAD                          C(025)    Unloading Point
                    WEMPF                          C(012)    Goods Recipient
                    PS_POSID                       C(024)    Work Breakdown Structure Element (WBS Element)
                    KOSTL                          C(011)    COST_CTR v bapito ?
                    NAME1                          C(040)    Name1 - Name of an address
                    NAME2                          C(040)    Name2 - Name of an address 2
                    STREET                         C(060)    Street
                    DELIVERY_DATE                  C(008)    Date on which the goods are to be delivered
                    TEXT                           C(132)    item text
    STRUCTURE RELATIONS :
    Structure Relations
    E1PREQCR              Header segment                                               <<<< UPFILE  upload file
               E1BPEBANC             Transfer Structure: Create Requisition Item                  <<<< UPFILE2 123
               E1BPEBKN              Transfer Structure: Create/Display Requisition Acct Assgt    <<<< UPFILE2 123
               E1BPEBANTX            BAPI Purchase Requisition: Item Text                         <<<< UPFILE2 123
               E1BPESUHC             Communication Structure: Limits                              <<<< UPFILE2 123
               E1BPESUCC             Communication Structure: Contract Limits                     <<<< UPFILE2 123
               E1BPESLLC             Communication Structure: Create Service Line                 <<<< UPFILE2 123
               E1BPESKLC             Create Comm. Structure: Acct Assgt Distr. for Service Line   <<<< UPFILE2 123
               E1BPESLLTX            BAPI Services Long Text                                      <<<< UPFILE  upload file
               E1BPMERQADDRDELIVERY  PO Item: Address Structure BAPIADDR1 for Inbound Delivery    <<<< UPFILE2 123
                   E1BPMERQADDRDELIVERY1 PO Item: Address Structure BAPIADDR1 for Inbound Delivery    <<<< UPFILE2 123
               E1BPPAREX             Ref. Structure for BAPI Parameter EXTENSIONIN/EXTENSIONOUT   <<<< UPFILE2 123
    MAINTAIN FIELD MAPPING AND... :
    the MAPPING between two IDOC`s segments:
    In first segment:
    E1BPEBANC                      Transfer Structure: Create Requisition Item
             Fields
                 PREQ_NO                      Purchase requisition number
                                     Source:  UPFILE2-BANFN (Purchase requisition number)
                                     Rule :   Transfer (MOVE)
                                     Code:    E1BPEBANC-PREQ_NO = UPFILE2-BANFN.
                 PREQ_ITEM                    Item number of purchase requisition
                                     Source:  UPFILE2-BNFPO (Item number of purchase requisition)
                                     Rule :   Transfer (MOVE)
                                     Code:    E1BPEBANC-PREQ_ITEM = UPFILE2-BNFPO.
    In second segment :
    E1BPEBKN                       Transfer Structure: Create/Display Requisition Acct Assgt
               Fields
                   PREQ_NO                      Purchase requisition number
                   PREQ_ITEM                    Item number of purchase requisition
                                       Source:  UPFILE2-BNFPO_FOR_MAP (Item number of purchase req. for MAPPING
                                       Rule :   Transfer (MOVE)
                                       Code:    E1BPEBKN-PREQ_ITEM = UPFILE2-BNFPO_FOR_MAP.
    After that everything was OK .

  • How to create one GR document for mutiple Purchase orders

    Can you please explain me in SAP - How to create one Goods Receipt document for reference of Multiple purchase orders.

    Dear Tanuj,
    Both Rama & Stephen are correct.
    You can take Single GR for Multiple PO either in MIGO or MB01 as long as that POs belongs to same vendor.
    In MIGO, after putting the PO press,enter,  again give the next PO of that vendor .
    If this solve your problem, close the issue.
    With Regars,
    Krishna Reddy

Maybe you are looking for