![]() Step 4: Call FM ‘ARCHIV_WORKFLOW_COMMIT’ and pass the import parameters as shown below. Here, we can use AP document’s object key (BKPF-AWKEY) ![]() target AP document to which attachment link needs to be created). ![]() Step 3: Prepare target object W_BKPF_OBJECT (i.e. Step 2: Call FM ‘ARCHIV_GET_CONNECTIONS’ using source object key to get the attachment document link into internal table T_TOAV0. Step 1: Use the object key (BKPF-AWKEY) of the AR document to prepare source object W_OBJECT Please refer the code for the variables mentioned here. Please find the code which is added as attachment along with document. In storage mode select “Print and Archive” and give the document type that was created in transaction OAC2. Step 3: Go to transaction NACE and select the output type for this process is followed. Here in this example, link table ‘TOA01’ is used. Performs file compression, extraction, etc. Here Billing document (VBRK) and Accounting document (BKPF) will be linked with a test content repository ‘TN’. Read B1 Free Archiver review which is available as a free download for Windows. Step 2: Go to Transaction OAC3 and create a link for content repository. It supports more than 30 formats, including popular ones such as RAR, RAR5, ZIP, and 7Z. It supports all modern compression formats with a clean UI to make extraction a breeze. Here, the kind of attachment which we intend to transfer is PDF. Bandizip is another feature-loaded RAR opener for both Windows and Mac users. Step 1: Go to Transaction OAC2 and create a new document type as shown below. Coding part to do the linking of attachment Also, changing the setting for the message type in transaction NACEī. Configuration of Document Type and linking the content repository in T-Codes – OAC2 and OAC3 respectively.The linking of this attachment between the documents involves two steps, Here, if you notice, the attachment from AR document is transferred to the newly posted AP document. When this document is posted, workflow will be triggered to post the AP document and the transfer of attachment will happen.ĪP document posted in the partner company code 3277 along with attachment is given as example below. The trading partner company code for this Customer is 3277. The attachment can also be seen along with the AR document. This document will explain this process.īelow screen shot shows the AR document posted (in Company code – 0774) which is generated upon Billing. But how to transfer the attachment from AR document to AP document posted in SAP. Using workflow, AP documents in partner company code can be posted. In cross company trading scenario, when this document is generated, there may arise a requirement to post a corresponding AP document (Account Payable) on the partner company code. ![]() Accounts receivable document) will be generated when billing is done (T-code VF01). But in this document, I have taken a scenario of cross company posting to explain this process. The linking of attachments between SAP documents will be required in many business scenarios in SAP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |