INVOICE에 PREPAYMENT를 APPLY한 후의 DATA FLOW

제품 : FIN_AP
작성날짜 : 2004-05-19
INVOICE에 PREPAYMENT를 APPLY한 후의 DATA FLOW
========================================
PURPOSE
Invoice에 Prepayment를 Apply한 후의 Data변화에 대해서
간략하게 설명합니다.
Explanation
승인 및 Accounting처리가 끝난 Invoice에 대해서 Prepayment를 Apply하게되면,
승인상태는 "Need reapproval"이고, Accounted상태는 "Partial"로 바뀌게 됩니다.
그 후에 Approve작업 및 Accounting작업을 하면,
다시 "Approved"와 "Yes"로 바뀌게 되고, 그 후에 Prepayment unapply하게되면,
다시 상태는 "Need Reapproval"과 "Partial"로 바뀝니다.
Table level에서는 Accounting전까지는 송장 Main table, 즉,
AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_PAYMENT_SCHEDULES_ALL 등의
특정 column값들만 변하게 되고, Accounting생성작업이 실행되면,
Event와 AP_AE_HEADERS_ALL, AP_AE_LINES_ALL table등에 각각의 Event data가
발생하게 됩니다.
즉, Invoice, Prepayment Apply, Prepayment unapply 등과 같은 Event data가 발생합니다.

Similar Messages

AR DATA FLOW (TABLE LEVEL) - INVOICE편

제품 : FIN_AR
작성날짜 : 2003-09-16
AR DATA FLOW (TABLE LEVEL) - INVOICE편
=====================================
PURPOSE
이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
설명한다.
Invoice transaction을 기준으로 설명한다.
Explanation
1. Invoice
User가 invoice를 입력하면, 아래의 table들에 data가 insert된다.
o RA_CUSTOMER_TRX_ALL (Invoice Header)
o RA_CUSTOMER_TRX_LINES_ALL (Line Details)
o RA_CUST_TRX_LINE_GL_DIST_ALL (Information for posting to GL)
o RA_CUST_TRX_LINES_SALESREPS_ALL (Sales Credit Information)
일단, invoice가 "Complete"되면, 아래의 table에 한줄(혹은 그 이상)이
추가로 Insert된다.
o AR_PAYMENT_SCHEDULES_ALL (Running Totals for Invoice Amounts)
대체로 하나의 invoice는 하나의 Payment schedule record를 가지지만,
만약 할부(Installment)로 Pay처리되는 invoice라면, installment하나당
하나의 Payment schedule record를 가진다.
| | /| |
| TRX |---------------<-| PAYMENT |
| | \| SCHEDULE |
| |
| |
^ -------
/|\ |
------------ |
| | |
| TRX_LINES | |
_| | |
/ ------------ |
| | | |
\__/ | |
^ |
/|\ |
| |
| GL_DIST |
| |
1.1 RA_CUSTOMER_TRX_ALL
Invoice의 Header정보(Customer, Invoice Number, date.. etc)를 담고 있는 table이다.
Invoice하나당 한줄의 정보가 Insert된다.
Key = CUSTOMER_TRX_ID (generated from sequence RA_CUSTOMER_TRX_S)
Important Fields
TRX_NUMBER - User Entered Invoice Number
CUST_TRX_TYPE_ID - Foreign key to RA_CUST_TRX_TYPES
BILL_TO_CUSTOMER_ID - Foreign Key to RA_CUSTOMERS
SHIP_TO_CUSTOMER_ID - Foreign key to RA_CUSTOMERS
TRX_DATE - Invoice Date
COMPLETE_FLAG - Y or N
1.2 RA_CUSTOMER_TRX_LINES_ALL
Invoice의 Line정보(수금 item및 금액, Tax등)가 insert되는 table이다.
Invoice하나당 한줄이상을 가진다.
Key = RA_CUSTOMER_TRX_LINE_ID (from sequence RA_CUSTOMER_TRX_LINES_S)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
LINE_TYPE - LINE, TAX, FREIGHT
QUANTITY_INVOICED - Line Quantity
UNIT_SELLING_PRICE - Price per unit
EXTENDED_AMOUNT - Quantity * Price
LINK_TO_CUST_TRX_LINE_ID - Null for LINE, for TAX and FREIGHT lines
contains the RA_CUSTOMER_TRX_LINE_ID of
associated LINE record
1.3 RA_CUST_TRX_LINE_GL_DIST_ALL
GL로 Posting될 정보가 담겨져 있다.
Invoice Line당 한줄 + Invoice Header 한줄로 이루어져 있다.
(예를들어, Invoice의 Line이 총 3줄이라면, RA_CUST_TRX_LINE_GL_DIST_ALL table에는 총 4줄의 정보가 담기게 된다.)
Key = CUST_TRX_LINE_GL_DIST_ID (from sequence)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
CUSTOMER_TRX_LINE_ID - Foreign key to RA_CUSTOMER_TRX_LINES or
Null if this relates to Invoice Header.
AMOUNT - Value of distribution - entered currency
ACCOUNTED_AMOUNT - Value of distribution - book currency
CODE_COMBINATION_ID - Foreign key to GL_CODE_COMBINATIONS
POSTING_CONTROL_ID - -3 if unposted
GL_DATE - Accounting date.
GL_POSTED_DATE - Date Invoice posted to GL.
1.4 RA_CUST_TRX_LINE_SALESREPS_ALL
해당 invoice가 입력될때 함께 입력된 Sales Person에 대한 정보가
담겨져 있다.
1.5 AR_PAYMENT_SCHEDULES_ALL
해당 invoice에 대해서 Line, Tax, 운송비 등 각각의 항목에 대한 Total값과
Remaining값을 담고 있다.
대체로 Invoice당 한줄이 insert된다.
Key = PAYMENT_SCHEDULE_ID (from sequence AR_PAYMENT_SCHEDULES_S)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
STATUS - (OP)en or (CL)losed
ACTUAL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise
date payment schedule closed.
GL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise the
gl date of the closing transaction.
AMOUNT_DUE_ORIGINAL - Invoice Total Amount
AMOUNT_DUE_REMAINING - Total Amount outstanding for Invoice.
AMOUNT_LINE_ITEMS_ORIGINAL - Sum of Invoice Line amounts.
AMOUNT_LINE_ITEMS_REMAINING - Outstanding Line amounts.
TAX_ORIGINAL - Total Tax for Invoice.
TAX_REMAINING - Outstanding Tax for Invoice
FREIGHT_ORIGINAL - Total Freight For Invoice
FREIGHT_REMAINING - Outstanding Freight
AMOUNT_APPLIED - Total payments applied to this Invoice.
AMOUNT_CREDITED - Total Credit Memos applied.
AMOUNT_ADJUSTED - Total value of adjustments.
The payment schedule should balance within itself, ie the following
calculations
should be true:-
AMOUNT_DUE_ORIGINAL = AMOUNT_LINE_ITEMS_ORIGINAL
+ TAX_ORIGINAL
+ FREIGHT_ORIGINAL
AMOUNT_DUE_REMAINING = AMOUNT_LINE_ITEMS_REMAINING
+ TAX_REMAINING
+ FREIGHT_REMAINING
AMOUNT_DUE_ORIGINAL = AMOUNT_DUE_REMAINING
+ AMOUNT_APPLIED
- AMOUNT_CREDITED
+ AMOUNT_ADJUSTED
Reference Documents
Note : 29277.1

Hello,
The basic flow of data is
ERP tables - source snapshots - source views (eg MRP_AP%) - staging tables (MSC_ST%) - ODS tables ( MSC%)
Check out note 412375.1. This is the flow for sales order data for ASCP.
regards
Geert

R11.0.3: An Invoice with future dated apyment data flow

제품 : FIN_AP
작성날짜 : 2003-11-18
R11.0.3: An Invoice with future dated apyment data flow
===============================================
PURPOSE
Future Dated Payment Term을 사용하는 Invoice의 Data Flow에 대해 살펴보도록 한다.
Explanation
accounting rule = accrual
.allowed future dated payment
1. Create a standard invoice (invoice amount: 2100, item amount: 2100, payment term : future dated payment)
And transfer it to GL.
* ap_invoice_distributions_all
accounting_date = 2003-11-11
accrual_posted_flag = Y
posted_flag = Y
* ap_trial_balance
accounting_date = 2003-11-11
distribution_amount = 2100
* 해당 data gl_interface table로 넘어감.
2. Posting these transferred journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted_dr = 2100 charge
accounted_cr = 2100 liability
3. Create a payment against this invoice with mature date = 12-nov-2003 and then transfer it to gl
* ap_invoice_payments_all
accounting_date = 2003-11-11
accrual_posted_flag = 'N'
posted_flag = 'N'
future_pay_posted_flag = 'Y'
* ap_payment_distributions_all
line_type_lookup_code = 'CASH'
* ap_trial_balance
accounting_date = 2003-11-11
payment_amount = 2100
* ap_checks_all
status_lookup_code = 'NEGOTIABLE'
4. Posting these payment journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted__cr : 2100 future pay
accounted_dr : 2100 liability
5. Clear this payment and then transfer to gl
Future dated payment 이고 Cash Management 를 사용하면 Cash Management 에서
Bank Reconcilation을 해주시면 됩니다.
Cash Management 를 사용하지 않으실 때는
"automatic clearing for future dated payment" 를 수행하여서 clear 를 해주어야 합니다.
이번 test case에서는 cash managemnt를 사용하지 않고 automatic clearing for
future dated payment 를 수행하여 clear 해주었습니다.
* ap_checks_all
status_lookup_code = 'CLEARED BUT UNACCOUNTED'
Cash Management를 사용하지 않기 때문에 status가 위와 같이 나타납니다.
Cash Management를 사용하면 option에 따라 status가 cleared나 reconciled로 변경 됩니다.
6. Transfer these cleared payment to gl and posting in gl
* 이 때에는 ap_trial_balance table에는 아무런 영향도 주지 않습니다.
* ap_invoice_payments_all
accrual_posted_flag = 'Y'
posted_flag = 'Y'
* gl_je_lines
accounted_dr= 2100 future pay
accounted_cr = 2100 cash
Example
Reference Documents
N/A

Rohini,
Thanks for your answer; I was out for few days and hence the delay.
What I am looking for is the complete usage model of the following ODS.
1> 0BBP_SC     we have figured it out
2> 0BBP_SCA    we have figured it out
3> 0BBP_DOC    we have figured it out
4> 0bbp_inv    we need help
     Looks like this can be populated from R3 using the following
Data Source    Info Source                    ODS Object
2LIS_02_ITM    2LIS_02_ITM                 0BBP_INV
2LIS_02_HDR    2LIS_02_HDR                0BBP_INV
5> 0BBP_DS     we need help
6> 0bbp_po     we need help
    The same combination is also used to populate the 0BBP_PO as well. We suspect that 0BBP_DS will then be populated from both 0BBP_INV and 0BBP_PO. At least that what we though after activating the BC and reading the sap help on BC for SRM.
We are doing a proof of concept and want to know all the ODS with data. We want to build an end to end (Shopping cart, approval, Doc flow, PO data with value, Invoice data with Value) and struggling to understand the model surrounding this three ODS ( 0bbp_inv, 0bbp_ds, 0bbp_po). Any help in this area will be appreciated.
Thanks
Arun

AR DATA FLOW (TABLE LEVEL) - ON ACCOUNT CREDITS & CASH RECEIPTS편

제품 : FIN_AR
작성날짜 : 2003-09-16
AR DATA FLOW (TABLE LEVEL) - ON ACCOUNT CREDITS & CASH RECEIPTS편
================================================================
PURPOSE
이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
설명한다.
On Account와 Cash Receipt을 기준으로 설명한다.
Explanation
1. On Account Credits
특정 Customer에 대한 Credit정보를 입력했으나, 아직 특정 Invoice에는 Apply되지 않은 정보를 "On Account" credit이라고 한다.
Credit정보가 들어있기 때문에, Credit Memo와 유사하게 table에 저장된다.
Credit Memo와 다른 점은 아래와 같다.
o When first entered the payment schedule will be fully remaining.
o When first entered no records are inserted into AR_RECEIVABLE_APPLI
CATIONS_ALL.
o The line records will have NULL values in
PREVIOUS_CUSTOMER_TRX_ID
PREVIOUS_CUSTOMER_TRX_LINE_ID
o The distribution lines have to be typed in as there is no invoice
to copy them from.
"On Account"는 같은 Supplier상에서는 어떠한 invoice에 대해서 적용이 가능하다는 점에서,
특정 invoice에만 apply가 가능한 Credit Memo와는 다르다.
2. Cash Receipts
Recipt정보가 입력되면, 아래의 table들에 insert된다.
o AR_CASH_RECEIPTS_ALL
o AR_CASH_RECEIPT_HISTORY_ALL
o AR_PAYMENT_SCHEDULES_ALL
o AR_RECEIVABLE_APPLICATIONS_ALL
입력된 Receipt정보가 특정 invoice와 match되면, 추가 record가
AR_RECEIVABLE_APPLICATIONS_ALL에 insert되고, AR_PAYMENT_SCHEDULE_ALL에는 update된다.
| | | |
| RECEIPT |------------------| PAYMENT |
| | | SCHEDULE |
| |
| |
^ ^
/|\ /|\
| | | |
| RECEIPT | |APPLICATIONS|
| HISTORY | | |
2.1 AR_CASH_RECEIPTS_ALL
Receipt에 대한 기본정보가 insert된다. 한 receipt당 한줄이 insert된다.
Key = CASH_RECEIPT_ID (from sequence AR_CASH_RECEIPTS_S)
Important Fields
AMOUNT - Value of receipt in entered currency
RECEIPT_NUMBER - Payment Number entered by user.
STATUS - (APP)lied, (UNAPP)lied, (REV)ersed Payment,
(STOP) payment, (NSF) insufficient funds.
It will only change to APP once the whole
amount of the receipt is applied.
REVERSAL_DATE - NULL unless receipt reversed
PAY_FROM_CUSTOMER - Contains CUSTOMER_ID for RA_CUSTOMERS
2.2 AR_CASH_RECEIPT_HISTORY_ALL
Receipt하나당 한줄의 data가 insert되고, GL로 Posting된 정보가 들어간다.
Receipt이 reverse되면, 새로운 row가 insert된다.
Key = CASH_RECEIPT_HISTORY_ID (from sequence)
Important Fields
CASH_RECEIPT_ID - Foreign key to AR_CASH_RECEIPTS record.
STATUS - CLEARED for manually input receipts.
GL_DATE - Accounting date
ACCOUNT_CODE_COMBINATION_ID - Key to GL_CODE_COMBINATIONS
POSTING_CONTROL_ID - -3 if unposted
REVERSAL_POSTING_CONTROL_ID - NULL unless payment reversed
CURRENT_RECORD_FLAG - Y if this is latest record
PRV_STAT_CASH_RECEIPT_HIST_ID - Key to previous receipt history record.
2.3 AR_PAYMENT_SCHEDULES_ALL
Invoice에 apply된 Total 금액정보가 저장된다.
Key = PAYMENT_SCHEDULE_ID (from sequence)
Important Fields
CUSTOMER_TRX_ID - NULL
CASH_RECEIPT_ID - Foreign key to AR_CASH_RECEIPTS record.
AMOUNT_DUE_ORIGINAL - Total amount of receipt (usually negative)
AMOUNT_DUE_REMAINING - Unapplied amount of receipt.
AMOUNT_APPLIED - How much of this receipt is applied .
STATUS - (OP)en or (CL)osed. Will only be closed if
AMOUNT_DUE_REMAINING is zero.
All of the fields holding LINE, TAX and FREIGHT amounts are NULL.
2.4 AR_RECEIVABLE_APPLICATIONS
Receipt이 처음 생성될때, 한줄의 data가 이 table에 insert되고,
invoice에 대해 Apply혹은 Unapply가발생하면, 두줄씩 새롭게 생성된다.
예를들면, 아래와 같다.
Record 1 UNAPP 700
{ Record 2 UNAPP -200
{ Record 3 APP 200 cross referenced to the Invoice
{ Record 4 UNAPP -500
{ Record 5 APP 500 cross referenced to 2nd Invoice
The sum of the amounts on records that have a particuar status should add up
to the running totals on the payment schedulesi, but with the opposite sign.
i.e. In the example above
AR_PAYMENT_SCHEDULES.AMOUNT_DUE_ORIGINAL = -700
AR_PAYMENT_SCHEDULES.AMOUNT_DUE_REMAINING = 0
AR_PAYMENT_SCHEDULES.AMOUNT_APPLIED = -700
UNAPP = 700 -200 -500 = 0
APP = 200 + 500 = 700
Statuses of these records can be:-
UNAPP - Unapplied
APP - Applied
ACC - On Account
UNID - Unidentified (Customer Not known)
이러한 record내역은 invoice/credit/receipt에 있는 Transaction History form에서 확인할 수 있다.
2.5 AR_PAYMENT_SCHEDULE (Invoice)
Receipt이 특정 invoice에 apply되면, invoice에 대한 Payment Schedule record가 update된다.
remaining amount field 값은 Payment금액만큼 줄어들게 된다.
만약, remaining amount가 "0"가 되면, invoice Payment schedule은 closed상태가 된다.
예를들어, Receipt금액 "200"이 "1175" invoice금액(Tax금액 175가 포함된)에 apply되었다면, Invoice의 Payment Schedule은 아래와 같이 조정된다.
Before After
AMOUNT_DUE_REMAINING 1175.00 975.00
AMOUNT_LINE_ITEMS_REMAINING 1000.00 800.00
TAX_REMAINING 175.00 175.00
FREIGHT_REMAINING 0.00 0.00
Note that receipts are applied in a fixed sequence:-
1. Line Amounts
2. Tax Amounts
3. Freight Amounts
ie The TAX_REMAINING figure will only start to decrease when the
AMOUNT_LINE_ITEMS_REMAINING is zero.
Reference Documents
Note : 29277.1 & 29278.1

Hi,
This query works fine for me:
SELECT CR.CASH_RECEIPT_ID,
 CR.RECEIPT_NUMBER,
 CR.RECEIPT_DATE,
 CR.CURRENCY_CODE,
 DECODE ( CR.TYPE, 'MISC', NULL, NVL (SUM (DECODE (RA.STATUS, 'ACC', NVL (RA.AMOUNT_APPLIED, 0), 0)), 0)) ON_ACCOUNT_AMOUNT
 FROM AR_RECEIVABLE_APPLICATIONS_ALL RA,
 AR_CASH_RECEIPTS_ALL CR,
 AR_RECEIPT_METHODS RM
 WHERE RA.CASH_RECEIPT_ID = CR.CASH_RECEIPT_ID
 AND CR.RECEIPT_METHOD_ID = RM.RECEIPT_METHOD_ID
 AND CR.ORG_ID = <org_id>
 GROUP BY CR.CASH_RECEIPT_ID,
 CR.RECEIPT_DATE,
 CR.RECEIPT_NUMBER,
 RM.NAME,
 CR.CURRENCY_CODE,
 CR.TYPE order by receipt_date desc
Let me know if it worked.
Octavio

Using asynchronous timer for data flow control

Hi all,
I am using system sleep to control the data flow (some digital lines and analog output). The pseudo code is something like this
Sleep(150);
// the following sections are exectuted in parallel
#pragma omp parallel sections
    #pragma omp section
      DAQmxWriteDigitalLines(...); // output TTL to one digitla line
    #pragma omp section
      DAQmxWriteDigitalLines(...); // output TTL to another digitla line
    #pragma omp section
      Sleep(2); // sleep 2ms
// the following sections are exectuted in parallel
#pragma omp parallel sections
    #pragma omp section
      DAQmxWriteDigitalLines(...); // output TTL to one digitla line
    #pragma omp section
      DAQmxWriteAnalogScalarF64(...); // analog output to one channel
    #pragma omp section
      Sleep(1); // delay 1ms
// the following sections are exectuted in parallel
#pragma omp parallel sections
    #pragma omp section
      DAQmxWriteDigitalLines(...); // output TTL to one digitla line
    #pragma omp section
      DAQmxWriteAnalogScalarF64(...); // analog output to one channel
#pragma omp section
      DAQmxWriteAnalogScalarF64(...); // analog output to another channel
    #pragma omp section
      Sleep(11); // delay 11ms
// ... other stuffs
I am running windows XP and I know it is not possible to get realtime control but I want a as precise timing as possible. Above code is not perfect but it works 95% of times. I just read an article about using the asynchronous timer to control the time delay. I try that idea with the following code frame
int CVICALLBACK ATCallback(int reserved, int timerId, int event, void *callbackData, int eventData1, int eventData2)
if (event==EVENT_TIMER_TICK)
int *nextdelay = (int *)callbackData;
SuspendAsyncTimerCallbacks();
if (timerId>=0)
double time;
if (*nextdelay==0) time=2.0;
else if (*nextdelay==1) time=1.0;
else time=12.0;
SetAsyncTimerAttribute(timerId, ASYNC_ATTR_INTERVAL, time);
if (*nextdelay==0)
#pragma omp parallel sections
#pragma omp section
DAQmxWriteDigitalLines(...); // output TTL to one digitla line
#pragma omp section
DAQmxWriteDigitalLines(...); // output TTL to another digitla line
*nextdelay++;
else if (*nextdelay==2)
#pragma omp parallel sections
#pragma omp section
DAQmxWriteDigitalLines(...); // output TTL to one digitla line
#pragma omp section
DAQmxWriteAnalogScalarF64(...); // analog output to one channel
*nextdelay++;
else if (*nextdelay==3)
#pragma omp parallel sections
#pragma omp section
DAQmxWriteDigitalLines(...); // output TTL to one digitla line
#pragma omp section
DAQmxWriteAnalogScalarF64(...); // analog output to one channel
#pragma omp section
DAQmxWriteAnalogScalarF64(...); // analog output to another channel
*nextdelay++;
ResumeAsyncTimerCallbacks();
return 0;
void main(void)
int n = 0;
int timeid;
timeid = NewAsyncTimer(120.0/1000.0, 3, 1, ATCallback, &n);
But it doesn't work. There is no compilation and runtime error but the timing just not right. I wonder do I have to suspend the timer in the callback function when I reset the delay for next call? If I do so, I am worry if it will apply too much delay (since I suspend and resume the timer in the delay) so it will cause even worse timing. But if I don't suspend the timer before I reset the time, what happen if the code running in the callback function not finished before the next callback arrive. It is quite confusing how to use asynchronous timer in this case. Thanks.

Yeah, unfortunately the 6711 doesn't have clocked digital I/O. There are only two counters anyway so even if you could use them to generate your signals you wouldn't have enough (*maybe* something with the 4 AO channels and a counter depending on what your output signals need to look like? The AO channels can output "digital" as well if you write 0V or 5V only).
A PCI DAQ card which does support clocked digital I/O and has 2 analog outputs is the 6221 (or if you could use PCIe the 6321 is a more updated version with two extra counters and some additional functionality).
If there isn't a way to implement clocked outputs afterall, one thing you could do to make your code a little more efficient is to consolidate the writes. You can put your digital lines into a single task and write them at ocne, and you can put your analog channels into a single task and write them at once as well.
I'm not sure about the callback issue, you might find some more help in the CVI forum. I don't think it's going to solve your underlying problem though as ultimately the execution timing of your software calls is at the mercy of your OS.
Best Regards,
John Passiak

Posting of cancelled Invoice after posting date is over

Hello Experts,
I am stuck up with a situation and as such seek your help.
A invoice was generated and the subsequent accounting document was also cleared. Now after the posting date was over, someone cancelled the invoice by T.code VF11 and as expected it didnt get posted .The document flow showing is as per below :
Order - open
Invoice - completed
Accounting Document - Cleared
Cancel Invoice - Open
Now, the business and their audit policies do not allow the client to cancel the invoice in back date ( within the posting period).
What are the options do we have to tackle the situation.
Joy

The issue has been temporarily addressed by changing the posting date.
However, now the client wants us to make an ABAP development so that no user is able to cancel the invoice after posting date is over. Now for that I have the following issues. Can someone please help me out in this.
The basic process details I am following is as per below:
For Transaction Code VF11 (i.e for Cancellation of Invoice) , when the invoice number which is subject to cancellation is provided, the System should search in VBRK table for the following :-
1)The System will at first search whether the entry exists or not. If the Entry is not valid then it should give an message u201C Document xxxxx does not Existu201D.This is in line to the existing practice.
2) If the Document number is valid then it will go to the billing date field and will fetch the value from the VBRK table . Then it will match whether the value fetched (i.e. this Invoice date) is in present posting period or not. The system can find the posting period from the table V_T001B.
a.If the Invoice date lies in the present posting period then the system will allow the cancellation document to be saved. This is in line to the existing process.
b.If the Invoice date lies beyond the present posting period then the system will not allow to save the cancellation of the Invoice with a pop up message of u201C The Document number subject to cancellation do not lie within the present posting periodu201D .
Now We have looked both the tables, from VBRK we will get Doc# and Billing date(FKDAT) but when we select Posting Date from table T001B( Permitted Posting Periods) there is some issue.
1. What will be the condition for selecting records from T001B table.Since there is multiple key fields
    RRCTY (Record Type) ,
    BUKRS (Posting Period Variant) ,
    MKOAR (Account Type or Masking)
    BKONT (To Account).
So, to get unique record what will be the value of this key fields. Is there any relationship with VBRK table ?
2. Which field I have to consider as Posting Date or Period. Because there are many fields related to Posting period.

How can I create a template of a Data Flow Task in SSDT?

The majority of the Data Flow Tasks that I build have the same five elements in them (OLE DB Source, Conditional Split, Derived Column, Data Conversion, and OLE DB Destination). I'd love to have a template of a Data Flow Task which already contains
these elements. Is that possible for me to create, and how do I do it?
I'm currently on SSDT 11.1, with Visual Studio Pro 2012.

Hi Tim_Dorenkamp,
If I understand correctly, you want to create a custom task, then add it as template of a Data Flow Task in SSIS Toolbox. So that you can use it in every packages.
Just as Samir suggested, we can developing a Custom Task that create a class that inherits from the Task base class, apply the DtsTaskAttribute attribute to your new class, and override the important methods and properties of the base class, including the
Execute method. The sample of create a custom task is for your reference:
http://microsoft-ssis.blogspot.com/2013/06/create-your-own-custom-task.html
Besides, as to your requirement, we can simply create a template package that including this Data Flow Task, then use this template to create new packages. If we want to use the Data Flow Task in an existing package, we can add a new package with the template,
then copy the Data Flow Task from the new package and paste it to the existing package. For more details about create a template package in SSIS, please refer to the following thread:
https://social.technet.microsoft.com/Forums/en-US/b0747467-daff-4fc8-9f81-20d68b38e5ee/change-default-for-package-protection-level?forum=sqlintegratio
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Losing source-target mapping from a data flow diagram process

Hi,
When I reload a model design from an xml repository, I am losing source-target mappings from a data flow diagram process. I wonder why.
The way it goes is:
- I define a data flow diagram with information stores, processes, and flows.
- Information structures are defined from the flows and the information trickles down to processes and information stores.
- In a process, I define Source-Target Mapping by selecting a target element and then selecting the source element(s).
- I save the whole model.
- So far, the Source-Target Mapping keeps the association between target and source elements.
- If I exit from Data Modeler, the next time I reload the saved model, the Source-Target Mapping target to source elements associations are lost!?
Does anyone have the same issue or would know how to resolve it?
Thanks,
/Mario

I am still having problems getting my source to target mappings to save after I apply the fix described in this thread. Any thoughts?
From my TargetElement.xml
<?xml version = '1.0' encoding = 'UTF-8'?>
<oracle.dbtools.crest.model.design.process.TargetElement parentClass="java.lang.Object">
<property name="objectID" dataType="java.lang.String" readOnly="true" defaultValue="" xmlName="id" xmlType="attribute" getter="getObjectID" setter="setObjectID" reffered="false"/>
<property name="target" dataType="oracle.dbtools.crest.model.design.DesignObject" defaultValue="" xmlName="target" xmlType="element" getter="getTarget" setter="setTarget" reffered="true"/>
<property name="description" dataType="java.lang.String" defaultValue="" xmlName="description" xmlType="element" getter="getDescription" setter="setDescription" reffered="false"/>
<property name="name" dataType="java.lang.String" readOnly="true" defaultValue="" xmlName="name" xmlType="attribute" getter="getName" setter="setName" reffered="false"/>
<property name="transformationType" dataType="java.lang.String" defaultValue="" xmlName="transformationType" xmlType="element" getter="getTransformationType" setter="setTransformationType" reffered="false"/>
<collection name="sources" dataType="java.util.List" xmlName="sources" itemXmlName="sourceRef" getter="getSources" itemIsRef="true" refsXMLName="sourceRefs" addItem="addSource" getItemByID="getSourceByID" nativeList="true" orderTheList="true"/>
<roproperty name="sources" dataType="interface java.util.List" getter="getSources"/>
</oracle.dbtools.crest.model.design.process.TargetElement>
Process.xml:
<?xml version="1.0" encoding="UTF-8" ?>
- <oracle.dbtools.crest.model.design.process.Process parentClass="oracle.dbtools.crest.model.design.process.Transformation">
<property name="type" dataType="int" defaultValue="0" xmlName="type" xmlType="element" getter="getType" setter="setType" reffered="false" />
<property name="batchMinimumTransactions" dataType="int" defaultValue="" xmlName="batchMinimumTransactions" xmlType="element" getter="getBatchMinimumTransactions" setter="setBatchMinimumTransactions" reffered="false" />
<property name="batchTimeUnit" dataType="java.lang.String" defaultValue="" xmlName="batchTimeUnit" xmlType="element" getter="getBatchTimeUnit" setter="setBatchTimeUnit" reffered="false" />
<property name="diagram" dataType="oracle.dbtools.crest.model.design.process.DataFlowDesign" defaultValue="" xmlName="diagram" xmlType="element" getter="getDiagram" setter="setDiagram" reffered="true" />
<property name="footNote" dataType="java.lang.String" defaultValue="" xmlName="footNote" xmlType="element" getter="getFootNote" setter="setFootNote" reffered="false" />
<property name="frequencyTimeUnit" dataType="java.lang.String" defaultValue="" xmlName="frequencyTimeUnit" xmlType="element" getter="getFrequencyTimeUnit" setter="setFrequencyTimeUnit" reffered="false" />
<property name="frequencyTimes" dataType="int" defaultValue="" xmlName="frequencyTimes" xmlType="element" getter="getFrequencyTimes" setter="setFrequencyTimes" reffered="false" />
<property name="interactiveLongestResponseTime" dataType="int" defaultValue="" xmlName="interactiveLongestResponseTime" xmlType="element" getter="getInteractiveLongestResponseTime" setter="setInteractiveLongestResponseTime" reffered="false" />
<property name="interactiveResponseTimeUnit" dataType="java.lang.String" defaultValue="" xmlName="interactiveResponseTimeUnit" xmlType="element" getter="getInteractiveResponseTimeUnit" setter="setInteractiveResponseTimeUnit" reffered="false" />
<property name="mode" dataType="java.lang.String" defaultValue="" xmlName="mode" xmlType="element" getter="getMode" setter="setMode" reffered="false" />
<property name="paramsWrappersString" dataType="java.lang.String" defaultValue="" xmlName="paramsWrappersString" xmlType="element" getter="getParamsWrappersString" setter="setParamsWrappersString" reffered="false" />
<property name="priority" dataType="java.lang.String" defaultValue="" xmlName="priority" xmlType="element" getter="getPriority" setter="setPriority" reffered="false" />
<property name="transformationtask" dataType="oracle.dbtools.crest.model.design.process.TransformationTask" defaultValue="" xmlName="transformationtask" xmlType="element" getter="getTransformationTask" setter="setTransformationTask" reffered="true" />
<property name="peakPeriodsString" dataType="java.lang.String" defaultValue="" xmlName="peakPeriodsString" xmlType="element" getter="getPeakPeriodsString" setter="setPeakPeriodsString" reffered="false" />
<collection name="events" dataType="java.util.List" xmlName="events" itemXmlName="eventRef" getter="getEvents" itemIsRef="true" refsXMLName="eventRefs" removeItem="removeEvent" addItem="addEvent" getItemByID="getPartyByID" nativeList="true" orderTheList="true" />
<collection name="targetMappings" dataType="java.util.List" xmlName="targetMappings" itemXmlName="targetMapping" getter="getTargetElements" createItem="createTargetElement" removeItem="removeEvent" addItem="addTargetElement" getItemByID="getPartyByID" nativeList="true" orderTheList="true" />
<roproperty name="componentFlowsFor" dataType="interface java.util.Collection" getter="getComponentFlowsFor" />
<roproperty name="events" dataType="interface java.util.List" getter="getEvents" />
<roproperty name="flowEvents" dataType="interface java.util.List" getter="getFlowEvents" />
<roproperty name="paramMapping" dataType="oracle.dbtools.crest.model.design.DesignObject" getter="getParamMapping" />
<roproperty name="paramsWrappers" dataType="interface java.util.List" getter="getParamsWrappers" />
<roproperty name="parentprocess" dataType="oracle.dbtools.crest.model.design.process.Process" getter="getParentProcess" />
<roproperty name="parentprocessInDFD" dataType="oracle.dbtools.crest.model.design.process.Process" getter="getParentProcessInDFD" />
<roproperty name="peakperiods" dataType="[Z" getter="getPeakPeriods" />
<roproperty name="processedAttributesAndFlows" dataType="interface java.util.List" getter="getProcessedAttributesAndFlows" />
<roproperty name="processedEntitiesAndFlows" dataType="interface java.util.List" getter="getProcessedEntitiesAndFlows" />
</oracle.dbtools.crest.model.design.process.Process>

AirPlay Data Flow?

Hello -
I'm about to purchase an Airport Express to connect to my home stereo receiver via audio-cable.
Planning to be able to output the sound usually coming out of my iPad thru my big stereo system, from Apps such as YouTube, Pandora, TuneIn Radio, Spotify, etc.
Wondering how much wifi data traffic this will cause and if it drains the iPad battery more quickly.
Could somebody please let me know which of the below two scenarios applies to Airplay. 1 or 2.
I will use the Spotify App as an example and seperate data into Music Data and Command Data. Command Data is things such as Play, Pause, Skip, Next, Volume, etc.
=================
(1)
Music data (~) flows as such
Spotify (in the Cloud) ~~> Airport Express (on my Wifi/or Ethernet, stereo system connected to Airport Express)
Command data (=) flows as such (Command Data is play, pause, skip, next, volume, etc.)
iOS Device ==> Airport Express ==> Spotify in the Cloud
=================
(2)
Music data (~) flows as such and Command Data (=) flow as such:
Spotify (in the Cloud) <~=~> iOS Device <~=~> Airport Express (on my Wifi/or Eithernet, stereo connected to Airport Express)
Basically, in option two, the music data would constantly flow thru the iOS device, draining it's batteries. Is this assumption correct?
Would greatly appreciate your help.
Thank you!
Ernst

It is important to note that AirPlay itself contains both the data & command streams.
(1)
Music data (~) flows as such
Spotify (in the Cloud) ~~> Airport Express (on my Wifi/or Ethernet, stereo system connected to Airport Express)
Command data (=) flows as such (Command Data is play, pause, skip, next, volume, etc.)
iOS Device ==> Airport Express ==> Spotify in the Cloud
Spotify would require a host device. As you know that could be a computer or iOS device. So, in your first flow diagram, Spotify cannot directly stream to an AirPort Express from the Cloud. Instead it would be like your flow diagram in item (2) of your post.
Both the Spotify App and the process of using AirPlay to stream to the Express would be the source of the battery drain as you suspected.

Data flows and technical terms

Hi all,
Anyone please give me SD data flow i.e what is sales order and when it will be generated and how it is linked with billing and delivery and what is invoice, cost centre, profit center, business area, wbs element etc.
And also the purchase data flow ie Purchase order purchase requisition, material document etc.
Provide me what exactly these mean in simple words.
I am new to BI and i am very confused with these technical terms.
Regards,
Nishuv.

Hi,
Cost centre & profit Centre Hierarchy:
you have to look at the Implementation Guide (IMG) for Profit Center Accounting, Master Data -> Create/Change/Display Hierarchy or something similar..with Transaction Code:KCH3 .
But if you want specfic one , need to build a specific hierarchy in R3 and load it in BW.
You can also build it directly in BW.
If it is product hierachy u have to generate the levels in R/3 side (using same transaction in SBIW), which activates PRODH1, PRODH2...etc.
SBIW or SAP reference IMG under General Logistics -> Master Material -> Material or Settings for Central Fields -> Sales-Relevant Data -> Define Product Hierarchies
Please check this link for the detailed procedure to create hiearchy;
http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm.
Create Hierarchy in R/3 -Sample
http://www.bwexpertonline.com/go/sample/
Pls chk this links;
Re: Hierarchy Loading from R/3 to BW
Product Hirarchies for 0MATERIAL (from R3)
R/3 Hierarchy Text upload issue
http://help.sap.com/saphelp_nw70/helpdata/en/b3/41cc373de44040e10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/c6/f3dc3709e9ea12e10000009b38f8cf/frameset.htm
Hope this helps,
Regards
CSM Reddy

Create Invoices on Specific Dates

Hello Gurus,
how to Create Invoices on Specific Dates? so all deliveries due for billing on a certain date can be
combined into one collective invoice.
Many thanks,
Frank

Hello Frank,
Yes, all deliveries due on a certain date can be combined into a single invoice, provided the following must be met:
1) the header data(like payment terms, payer,sales org, etc..) appearing in the billing document must agree
2) the split conditions specified do not apply.
I hope this helps.
Rgds,
Raghu.

COMM_SRTUCTURE is uknown when migrating data flow bw 3.x to 7.4

Dear ALL,
2LIS_13_VDHDR data flow migrating 3.x to 7.x , ABAP syntax error COMM_STRUCTURE is unknown infosoure transformation level, present we are using 7.4 sp5 . after migration ABAP code
TYPES:
      BEGIN OF _ty_s_TG_1_full,
*      InfoObject: 0CHNGID Change Run ID.
        CHNGID           TYPE /BI0/OICHNGID,
*      InfoObject: 0RECORDTP Record type.
        RECORDTP           TYPE /BI0/OIRECORDTP,
*      InfoObject: 0REQUID Request ID.
        REQUID           TYPE /BI0/OIREQUID,
*      InfoObject: 0CALDAY Calendar Day.
        CALDAY           TYPE /BI0/OICALDAY,
*      InfoObject: 0CALMONTH Calendar Year/Month.
        CALMONTH           TYPE /BI0/OICALMONTH,
*      InfoObject: 0CALWEEK Calendar year / week.
        CALWEEK           TYPE /BI0/OICALWEEK,
*      InfoObject: 0FISCPER Fiscal year / period.
        FISCPER           TYPE /BI0/OIFISCPER,
*      InfoObject: 0FISCVARNT Fiscal year variant.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
*      InfoObject: 0BILLTOPRTY Bill-to party.
        BILLTOPRTY           TYPE /BI0/OIBILLTOPRTY,
*      InfoObject: 0COMP_CODE Company code.
        COMP_CODE           TYPE /BI0/OICOMP_CODE,
*      InfoObject: 0DISTR_CHAN Distribution Channel.
        DISTR_CHAN           TYPE /BI0/OIDISTR_CHAN,
*      InfoObject: 0DOC_CATEG Sales Document Category.
        DOC_CATEG           TYPE /BI0/OIDOC_CATEG,
*      InfoObject: 0PLANT Plant.
        PLANT           TYPE /BI0/OIPLANT,
*      InfoObject: 0SALESORG Sales Organization.
        SALESORG           TYPE /BI0/OISALESORG,
*      InfoObject: 0SALES_GRP Sales group.
        SALES_GRP           TYPE /BI0/OISALES_GRP,
*      InfoObject: 0SALES_OFF Sales Office.
        SALES_OFF           TYPE /BI0/OISALES_OFF,
*      InfoObject: 0SHIP_TO Ship-To Party.
        SHIP_TO           TYPE /BI0/OISHIP_TO,
*      InfoObject: 0SOLD_TO Sold-to party.
        SOLD_TO           TYPE /BI0/OISOLD_TO,
*      InfoObject: 0VERSION Version.
        VERSION           TYPE /BI0/OIVERSION,
*      InfoObject: 0VTYPE Value Type for Reporting.
        VTYPE           TYPE /BI0/OIVTYPE,
*      InfoObject: 0DIVISION Division.
        DIVISION           TYPE /BI0/OIDIVISION,
*      InfoObject: 0MATERIAL Material.
        MATERIAL           TYPE /BI0/OIMATERIAL,
*      InfoObject: 0SHIP_POINT Shipping point.
        SHIP_POINT           TYPE /BI0/OISHIP_POINT,
*      InfoObject: 0PAYER Payer.
        PAYER           TYPE /BI0/OIPAYER,
*      InfoObject: 0DOC_CLASS Document category /Quotation/Order/Deliver
*y/Invoice.
        DOC_CLASS           TYPE /BI0/OIDOC_CLASS,
*      InfoObject: 0DEB_CRED Credit/debit posting (C/D).
        DEB_CRED           TYPE /BI0/OIDEB_CRED,
*      InfoObject: 0SALESEMPLY Sales Representative.
        SALESEMPLY           TYPE /BI0/OISALESEMPLY,
*      InfoObject: 0SUBTOT_1S Subtotal 1 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_1S           TYPE /BI0/OISUBTOT_1S,
*      InfoObject: 0SUBTOT_2S Subtotal 2 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_2S           TYPE /BI0/OISUBTOT_2S,
*      InfoObject: 0SUBTOT_3S Subtotal 3 from pricing proced.for conditi
*on in stat. curr..
        SUBTOT_3S           TYPE /BI0/OISUBTOT_3S,
*      InfoObject: 0SUBTOT_4S Subtotal 4 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_4S           TYPE /BI0/OISUBTOT_4S,
*      InfoObject: 0SUBTOT_5S Subtotal 5 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_5S           TYPE /BI0/OISUBTOT_5S,
*      InfoObject: 0SUBTOT_6S Subtotal 6 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_6S           TYPE /BI0/OISUBTOT_6S,
*      InfoObject: 0OPORDQTYBM Open orders quantity in base unit of meas
*ure.
        OPORDQTYBM           TYPE /BI0/OIOPORDQTYBM,
*      InfoObject: 0OPORDVALSC Net value of open orders in statistics cu
*rrency.
        OPORDVALSC           TYPE /BI0/OIOPORDVALSC,
*      InfoObject: 0QUANT_B Quantity in base units of measure.
        QUANT_B           TYPE /BI0/OIQUANT_B,
*      InfoObject: 0DOCUMENTS No. of docs.
        DOCUMENTS           TYPE /BI0/OIDOCUMENTS,
*      InfoObject: 0DOC_ITEMS Number of Document Items.
        DOC_ITEMS           TYPE /BI0/OIDOC_ITEMS,
*      InfoObject: 0NET_VAL_S Net value in statistics currency.
        NET_VAL_S           TYPE /BI0/OINET_VAL_S,
*      InfoObject: 0COST_VAL_S Cost in statistics currency.
        COST_VAL_S           TYPE /BI0/OICOST_VAL_S,
*      InfoObject: 0GR_WT_KG Gross weight in kilograms.
        GR_WT_KG           TYPE /BI0/OIGR_WT_KG,
*      InfoObject: 0NT_WT_KG Net weight in kilograms.
        NT_WT_KG           TYPE /BI0/OINT_WT_KG,
*      InfoObject: 0VOLUME_CDM Volume in cubic decimeters.
        VOLUME_CDM           TYPE /BI0/OIVOLUME_CDM,
*      InfoObject: 0HDCNT_LAST Number of Employees.
        HDCNT_LAST           TYPE /BI0/OIHDCNT_LAST,
*      InfoObject: 0CRM_PROD Product.
        CRM_PROD           TYPE /BI0/OICRM_PROD,
*      InfoObject: 0CP_CATEG Category.
        CP_CATEG           TYPE /BI0/OICP_CATEG,
*      InfoObject: 0FISCYEAR Fiscal year.
        FISCYEAR           TYPE /BI0/OIFISCYEAR,
*      InfoObject: 0BP_GRP BP: Business Partner Group (from Hierarchy).
        BP_GRP           TYPE /BI0/OIBP_GRP,
*      InfoObject: 0STAT_CURR Statistics Currency.
        STAT_CURR           TYPE /BI0/OISTAT_CURR,
*      InfoObject: 0BASE_UOM Base Unit of Measure.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
*      InfoObject: 0PROD_CATEG Product Category.
        PROD_CATEG           TYPE /BI0/OIPROD_CATEG,
*      InfoObject: 0VOLUME Volume.
        VOLUME           TYPE /BI0/OIVOLUME,
*      InfoObject: 0VOLUMEUNIT Volume unit.
        VOLUMEUNIT           TYPE /BI0/OIVOLUMEUNIT,
*      InfoObject: 0FISCPER3 Posting period.
        FISCPER3           TYPE /BI0/OIFISCPER3,
*      InfoObject: 0SALES_DIST Sales District.
        SALES_DIST           TYPE /BI0/OISALES_DIST,
*      InfoObject: 0BILL_TYPE Billing type.
        BILL_TYPE           TYPE /BI0/OIBILL_TYPE,
*      InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
        MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
*      InfoObject: 0SHIP_COND Shipping conditions.
        SHIP_COND           TYPE /BI0/OISHIP_COND,
*      InfoObject: 0AB_RFBSK Status for Transfer to Accounting.
        AB_RFBSK           TYPE /BI0/OIAB_RFBSK,
*      InfoObject: 0AB_FKSTO Indicator: Document Is Cancelled.
        AB_FKSTO           TYPE /BI0/OIAB_FKSTO,
*      InfoObject: 0CUST_GRP5 Customer Group 5.
        CUST_GRP5           TYPE /BI0/OICUST_GRP5,
*      InfoObject: ZCU_COND1 Constomer Condition Group 1.
        /BIC/ZCU_COND1           TYPE /BIC/OIZCU_COND1,
*      InfoObject: ZCU_COND2 Customer Condition Group 2.
        /BIC/ZCU_COND2           TYPE /BIC/OIZCU_COND2,
*      InfoObject: ZBATCHCD Batch Code.
        /BIC/ZBATCHCD           TYPE /BIC/OIZBATCHCD,
*      InfoObject: 0BATCH Batch number.
        BATCH           TYPE /BI0/OIBATCH,
*      InfoObject: ZBATCH Batch number.
        /BIC/ZBATCH           TYPE /BIC/OIZBATCH,
*      Field: RECORD Data record number.
        RECORD           TYPE RSARECORD,
      END   OF _ty_s_TG_1_full.
* Additional declaration for update rule interface
DATA:
    MONITOR       type standard table of rsmonitor WITH HEADER LINE,
    MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
    RECORD_NO     LIKE SY-TABIX,
    RECORD_ALL    LIKE SY-TABIX,
    SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
* global definitions from update rules
* TABLES: ...
DATA: IN    TYPE F,
      OUT   TYPE F,
      DENOM TYPE F,
      NUMER TYPE F.
* Def. of 'credit-documents': following doc.categ. are 'credit docs'
*   reversal invoice (N)
*   credit memo (O)
*   internal credit memo (6)
* Credit-documents are delivered with negative sign. Sign is switched
* to positive to provide positive key-figures in the cube.
* The combination of characteristics DE_CRED and DOC-CLASS provides
* a comfortable way to distinguisch e.g. positive incoming orders or
* order returns.
* Def. der 'Soll-Dokumente': folgende Belegtypen sind 'Soll-Belege'
*   Storno Rechnung (N)
*   Gutschrift (O)
*   Interne Verrechn. Gutschr. (6)
* Soll-Dokumente werden mit negativem Vorzeichen geliefert. Um die Kenn-
* zahlen positiv in den Cube zu schreiben, wird das Vorzeich. gedreht
* Die Kombination der Merkmale DEB_CRED und DOC-CLASS gibt Ihnen die
* Möglichkeit schnell z.B. zwischen Auftrags-Eingang oder Retouren zu
* unterscheiden.
DATA: DEB_CRED(3) TYPE C VALUE 'NO6'.
FORM routine_0002
TABLES
   P_MONITOR         structure rsmonitor
CHANGING
    RESULT         TYPE _ty_s_TG_1_full-DOCUMENTS
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
CLEAR RESULT.
RESULT = COMM_STRUCTURE-NO_INV.
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
   RESULT = RESULT * ( -1 ).
ENDIF.
RETURNCODE = 0.
p_monitor[] = MONITOR[].
CLEAR:
    MONITOR[].
ENDFORM.                    "routine_0002
FORM routine_0003
TABLES
   P_MONITOR         structure rsmonitor
CHANGING
    RESULT         TYPE _ty_s_TG_1_full-DEB_CRED
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
    RESULT = 'C'.
ELSE.
    RESULT = 'D'.
ENDIF.
RETURNCODE = 0.
p_monitor[] = MONITOR[].
CLEAR:
    MONITOR[].
ENDFORM.
Error:
E:Field "COMM_STRUCTURE-NO_INV" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement.
communication structure chaged to sours fields but no uses , please suggest how can i proceed , Thanks in Advance immediate replay
Thanks & Regards
Ramesh G

Hi Gareth,
You have two options:
1. Transport from BW 3.1 to BI 7.0. You'll need to create a transport route between both systems. This may cause you some troubles in the future when you want to modify the objects you transported.
2. As there are few objects, you can use XML export utility from Transport connection. There, you make an XML file with the objects you need to transport. One thing that you may take care of, in this option, is that the business content objects you are exporting need to be activated in the destination system. Another problem is that querys are not exported.
Since it's only a cube, maybe you can create the objects manually. Look that in BI 7.0 there are several new functionalities, i don't know how transport or xml export would work.
Hope this helps.
Regards,
Diego

MM data flow

My dear Friends,
I want Data flow Co with SD and MM with examples please..
Amruta.
Email : - [email protected]

Hi,
Link Between SAP SD, MM & FI
1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc.
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points Module
Availability Check - MM
Credit Check - FI
Costing - CO/ MM
Tax Determination - FI
Transfer of Requirements - PP/ MM
Delivery & Goods Issue
Integration Points Module
Availability Check - MM
Credit Check - FI
Reduces stock - MM
Reduces Inventory $ - FI/ CO
Requirement Eliminated - PP/ MM
Billing -
Integration Points Module
Debit A/R - FI/ CO
Credit Revenue - FI/ CO
Updates G/ L - FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing - PS
Return Delivery & Credit Memo -
Integration Points Module
Increases Inventory - MM
Updates G/ L - FI
Credit Memo - FI
Adjustment to A/R - FI
Reduces Revenue - FI
SD Transaction Code Flow:
Inquiry / Document type IN
Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT
Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR
Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
Delivery LF
Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
Billing MN
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
To create vendor tcode is
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
Reward if useful.
Chandru.
Message was edited by:
 CHANDRAMOHAN NATARAJAN

Required, SD DATA FLOW with MM Integration.

Dear Experts,
I have used the search functionality.. but got links..
Please Explain in your words, 1.SD Data Flow.
and also please mention its Integration with MM.
Points Assured.
Thanks

Link Between SAP SD, MM & FI
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Costing                        -       CO/ MM
Tax Determination              -       FI
Transfer of Requirements       -       PP/ MM
Delivery & Goods Issue
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Reduces stock                  -       MM
Reduces Inventory $            -       FI/ CO
Requirement Eliminated         -       PP/ MM
Billing -
Integration Points                      Module
Debit A/R                      -       FI/ CO
Credit Revenue                 -       FI/ CO
Updates G/ L                   -       FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing              -       PS
Return Delivery & Credit Memo -
Integration Points                      Module
Increases Inventory            -       MM
Updates G/ L                   -       FI
Credit Memo                    -       FI
Adjustment to A/R              -       FI
Reduces Revenue                -       FI
SD Transaction Code Flow:
Inquiry / Document type IN
Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT
Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
Sales Order OR
Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
Delivery LF
Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
Billing F2
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
Regards,
Rajesh Banka
Reward suitable points.

Data Flow is not working in Workflow

Hello!
I want to start my workflow with 'SAPI_WAPI_CREATE_EVENT'.
But the workflow is not starting because it has error in the data flow of its task. Goal of the workflow is that the event send an email to the employee.
what should i do in the data flow? what have I put in the data flow?

I created an ABAP-Class with the event 'create_wf' and the method 'create_workflow' .
This class includes the interfaces bi_object, bi_persistent and if_workflow.
My method 'create_workflow' call the FM 'SAP_WAPI_CREATE_EVENT'. But what are the exporting parameter 'object_type' and object_key' and 'event'? Is 'event' my own event 'create_wf'? And where I define the event? (My report calling the method 'create_workflow'. Is this the definition?)
In my workflow I have the task and I don't know which objects or parameters to put in in the data flow? In the task (flag 'basic data') I have the object category APAB class with the object type 'zsieb_startwf' (name of my class) and the method i explaind before 'create_wf' (which is my event in the class)'. in the flag event trigger I put the same data again.
Did I forget anything?
Where do I integrate my workflow in my class? Or is this unnecessary?
Hope, you understand now my problem better.
Hi Anna,
I think you may be confusing 'events' as they relate to Workflow and 'events' as they exist in classes.
There is a table which contains business object related events, SWETYPV. This provides the linkage between your business object (such as Invoice, BUS2081, or Purchase Order, BUS2012) and Event (Created, Changed, etc) and your workflow.
You need to know what object type and what event (in the workflow context) are required before you can proceed.
So if you are trying to start a workflow from SAP_WAPI_CREATE_EVENT, your import parameters might be:
call function 'SAP_WAPI_CREATE_EVENT'
    exporting
      object_type             = 'BUS2081'
      object_key              = yourdocumentkey
      event                       = 'CREATED'
      commit_work             = 'X'
      event_language          = sy-langu
    importing
      return_code             = lv_retcode
      event_id                = lv_eventid.
Then, in transaction SWETYPV, you would have an entry linking the Object/Event pair to the 'receiver' - the Workflow Template, and use a Receiver Function Module such as SWW_WI_CREATE_VIA_EVENT_IBF to actually raise the event.
Regards,
Sue

INVOICE에 PREPAYMENT를 APPLY한 후의 DATA FLOW

Similar Messages

Maybe you are looking for