Validating audio data message

My Audio is out of sync on capture, if I cancel the validating audio data message it seems to be fine. Any help would be great as I would like to know what I'm doing wrong. Never seen this message in 5 years of editing in FCP

12 bit. Haven't been having any audio problems with FCE. However, I tried the nightmare iDive and never got audio (much less anything else) to work with that. So I uninstalled it and asked for my money back.

Similar Messages

FCE crashes after validating audio data

I have just started using FCE and I'm having a problem with it craahing. I am capturing from a DV tape that was recorded in 12bit audio. I got the audio synch warning message a few times and, after reading the manual, realized that I needed to change the NTSC setting in Easy Setup to NTSC 32kHz for 12 bit audio, which I did.
I used the Capture Now button and pressd the Esc key to stop the capture. If the clip I capture is several minutes long I get a small window titled "Analyzing DV Audio" and the text in the window says "Validating Audio Data". This window remains in view for a minute or more and then FCE crashes. I have tried this several times and get the same result. I tried repairing permissions and rebooting and still it crashes. Any suggestions would be appreciated.
Bob Switzer
G4 Dual 867 Mac OS X (10.4.7)
G4 Dual 867 Mac OS X (10.4.7)

Thanks for your suggestion. I trashed all the prefs and tried capturing the same footage again and experienced another crash. I then moved to another section of the tape and tried again and it worked without crashing. I also captured footage from another tape without a problem. I suspect that particular section of tape is somehow corrupted and was causing the crash. I was able to take this section of tape into iMovie without a problem. I guess I'll bring it into FCE from iMovie.
Thanks again for your help.
G4 Dual 867 Mac OS X (10.4.7)

Analyzing DV Audio - Validating Audio Data

Sony UVW-1600 through ADS Pyro A/VLINK using S-Video in/Firewire 400 out
Audio through Alesis MultiMix 8 USB mixer - 44.1 kHz output only
Just did clean install of Snow Leopard, reinstall/updates on FCP
Otherwise same configuration as before but lost original Custom AV settings and Easy Setups.
Now when I capture BetaSP material, video through the A/VLINK and audio through the Alesis, I'm getting messages I never used to get:
If I set my Capture Preset to 48 kHz audio, at close of capture I get "Analyzing DV Audio - Validating Audio Data"
If I set my Capture Preset to 44.1 kHz (matching the Alesis output), I get a long message saying the audio data rate of my captured media file doesn't match the sample rate on my source file.
From checking old captured clips, I see that I've always been capturing at 48 kHz but never got the "Analyzing DV Audio" message before. Not seeing any sync problems.
Anyone know why I'm suddenly getting this message? I don't want to capture audio through the DV stream as my source tape levels are all over the place. Thanks

Okay, I've answered my own question (I think) but could be helpful to others: in setting up my replacement (after the reinstall) Capture Preset I made a custom preset that selected "USB Audio Codec" for "Quicktime Audio Settings Device." So FCP was seeing video come in through the Firewire stream and audio through the USB stream. It evidently wanted to "validate" the rejoining of the two. I've just changed that Quicktime Audio Settings Device back to DV Audio and now I don't get the validating message. In OS X System Preferences I have "USB Codec" chosen for default audio input so FCP must be using that setting but "thinks" it's getting audio from the Firewire DV stream. I'd tried that earlier but lost audio completely during FCP capture. Now it's working. Odd...

Restriction of Validity start date in Scheduling agreement

Hi,
I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting back validity start date in the header of Scheduling agreement (me32l)
What can be the possible reason.
Regards
Sachin

Hi,
I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
Laufzeitbeginn in der Vergangenheit -
    IF ekko-kdatb < sy-datlo.
      MESSAGE w170 INTO gl_dummy.
      mmpur_message 'W' '06' '170' '' '' '' ''.
Please consul your ABAP Team on this to change it to Error.
But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
Regards
Chandra Shekhar

Error: No valid complaint data was found in this sales area

Hi All,
I am getting below error while delta or request download of customer.
No valid complaint data was found in this sales area
Message no. CRM_SPL_BUPA_FRG0010203
Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Message no. SMW3018
Error case:
ECC-->Customer(Sold to) extended to a sales area and saved.
     CRM-->Business partner gets updated in the CRM properly.
ECC--> Deletion flag for same customer and same sales area is set. (Deletion flag - "Selected sales area").
     CRM-->Business partner gets updated in the CRM properly and is not shown as extended to the sales area via BP t code.
ECC-->Deletion flag is removed for the customer.
     CRM--> BDOC fails to update the Partner and goes in error.
Problem comes when deletion flag is removed in ECC.
Any help would be highly appreciated.
Thanks in advance.
-Ram

Hi Ram,
Hope you have not make any field mandatory in the Complaint tab in the sales area section in the BP.
When you are removing the deletion flag please check if any entry is mandatory in the Complaint tab.
Hope this will be useful
Thanks and Regards
DJ

"some audio data is no longer available"

How can I resolve this file problem?
I spent a couple of hours recording a narration as a STAP file that was about 30 minutes long. After the recording (the second action after "Empty File") I added several actions to delete unwanted portions (errors, repeats, etc.). To finalize the project I added a couple of actions (noise gate and limiter).
Everuthing appeared and played normally... but when I opened the file this morning I noticed that there was no audio in the project... scrolling up revealed that the "Recording" was unchecked... I checked it and got the following error message:
The action "Recording" has been disabled because some audio data is no longer available. You can replace this action with a similar action.<</div>
Replace? Does that mean repeating the work entirely?
Well, the file appears to be 591.8 MB in size... so it should have the audio in it.
Is there a way to recover the original audio from this file?
BTW, I should have exported it before closing it up... Unfortunately, not trusting your software is what I used to do with my PCs...
:o(

Never found the cause and did not check the package... so I decided to close the question. The event has not repeated itself as I have upgraded several times since.

Source List Validity Start Date

I have noticed that, if the source list validity start date and contract validity start date are same then, the contract price is not considered while creating PO and receive error message as "Source not included in list despite source list requirement"
If I change the validity start date of source list to one day before the validity start date of Contract then system is picking the contract price in PO and able to save PO successfully.
Is there any way to create PO even if the validity start date of source list and contract are same?

from OSS Note 44368 - ME51 ME57 Contract as source of supply
A contract that is valid on the delivery date but not on the current date is not taken into account in the source determination process.
Cause and prerequisites
This is programmed this way.
Solution
For reasons of upward compatibility, check will continue to be carried out on basis of current date.
However, if you wish the check to be against delivery date, you can implement the modification described under the advance corrections.
If Note 116464 is implemented in a 4.0B Release, use the advance correction from Release 4.5A, however, in Release 4.0B the program name is LMEQRF01.

Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

Hi,
How can I enable recipient validation work in this design:
2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
From Exchange documentation:
http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
Enable Anti-Spam Functionality on Mailbox Servers.
If You have a setup like this:
Install antispam agents:
Identity Enabled Priority
Transport Rule Agent True 1
Malware Agent True 2
Text Messaging Routing Agent True 3
Text Messaging Delivery Agent True 4
Content Filter Agent True 5
Sender Id Agent True 6
Sender Filter Agent True 7
Recipient Filter Agent True 8
Protocol Analysis Agent True 9
Have Recipient validation enabled:
Name Enabled RecipientValidationEnabled---- ------- --------------------------RecipientFilterConfig True True
Have AcceptedDomain AddressBook enabled:
DomainName DomainType AddressBookEnabled
contoso.com Authoritative True
Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
So .. HOW? Is it possible without Edge servers? Have I missed something?
I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
Sincerely,
Vince

Hello Vince,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Data validation for Date Field in Web Dynpro ABAP

Hi ,
In my WDA i want to perform data validation for date filed. (i.e. While creating a new record i have to check the Start Date should be always lesser than End Date.)
If u ll enter the wrong date it should validate the Date and throw an error message.
Please Reply soon its urgent.
Thanks,
Deepika

Hi,
First read the two attributes start date and end date.
Then write the following condition.
IF item_start_date > item_end_date.
Error message.
Endif.
For pop up error message you need to use Create_window method of the Interface if_wd_window.
Thanks.

Audio data to be acquired at 192khz

hi ...
well i have made a VI to acquire audio data and then write it to a file to furthur process it. the problem is that when i send stram of audio data upto 48 khz the data is captured continuously, but if i try to send a stream of 64khz or 192 khz the data is acquired but for a little time. i want to acquire data of 192khz stream continuously. i m using labview 6.2 and dio32hs card.
i want to acquire data at 192khz for atleast 6 min continuously.
is it possible???
please help..
thanx and regards
vivek modgil

Look at the producer consumer template for multithreading.
Essentially what happens if you use a simple model like
Initialize()
DaqLoop
   Read()
   Process()
   Display()
   Save()
LOOP
is that if the saving and/or sace takes too long the next itteration of read will have caused a buffer over run in the daq task. This is more evident in the faster Acquisition rates. Making the buffer larger only delays the onset of this event.
A better model is (Threads are just parallel loops)
Thread 1 (Producer):{
Initialize DAQ()
DaqLoop
   Read DAQ data() //all data avaliable.
   send data to a Queue
}Loop(until done)
Kill queue();
Thread 2 (Consumer):
DataLoop
Wait for data at queue; // put in some timeout ie 100ms
If new data-> Process() Display(); Save();
}Loop(While queue is valid)
This is just a starting point. Look at the producer/consumer model.
This ensures that the DAQ loop will (should) never overrun and the consumer loop will attempt to keep up with the data. Saving data to file is slow so do this post acquisition if possible (IE build array in memory).
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Please put a cost object with valid JV data for GL accoutnt (line 001)

Dear All,
When the user is trying to post ASKBN, They are getting an error saying "Please put a cost object with valid JV data for GL accoutnt (line 001)"
So we tried to look up the error, and the WBS, Cost center, profit center and JVA details are all available in place. Still cant understand why this error comes. And why the system is asking to put JV details when they are available.
On checking, WBS has an AUC and AUC has the cost center which has the JV details and PC details. So I think everything is in place.
Can someone help please and let us know if we are missing anything else that needs to be checked ?
Thanks,
Hari Dharen

Dear Hari Dharen,
if something else in missung you'll get a error message if you run ASKBN in testmodus.
regards Bernhard
Edited by: Bernhard Kirchner on Oct 5, 2010 8:55 AM

CIF of SA is not consistent for Validity End Date

Hello gurus,
Our company is quite new in using SNC, and we bumped into this problem (see description below), and hopefully this forum can help us.
<Description>:
When the Scheduling Agreement is CIFed from R/3 (ECC) to SNC, the Validity End Date does not get updated each time.
It gets updated sometimes, but not always. It is inconsistent behaviour.
<Example>:
Scheduling Agreement A
Validity End Date: 31.12.2012 Changed to 30.11.2012 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
Correctly updated the Validity End Date in SNC.
For the same Scheduling Agreement A updated Validity End Date to 31.01.2013 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
The Validity End Date was not updated in SNC & remained as 30.11.2012.
For the same Scheduling Agreement A updated Validity End Date to 15.10.2012 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
The Validity End Date was not updated in SNC & remained as 30.11.2012.
Thanks guys
Tuffy

Hi Tuffy,
1 - I am just wondering if after the Delete the existing External Procurement Relationship in SNC, and CFM1 and CFM2 the SA (i.e. changed my validity end date value) to the SNC, will the problem of the SNC side not able receive the changed SA??
When there is a change in the SA, integration model would create the same in SNC if it does not exist. But the transfer from ERP does not happen just like that. First, make sure that the message type (CIFSRC) has been checked in BD50 and then schedule a job to periodically transfer the SAs.
2 - What does the tcode the person in the SNC side have to double check to ensure the SA is transmitted there??
The t-code is /SAPAPO/MTI2 - External Procurement Relationship.
3 - Someone in our company advise BASIS team to check the transactions BD50 and BD52. What exactly does it mean and does it help?
This is correct. I mean guys who are responsible for Integration model need to set-up BD50, BD52 so that changes to SAs are transferred periodically.
Regards,
Sandeep

Valid To Date not available in BAPI_MATERIAL_BOM_GROUP_CREATE

HI All-
I am creating a BOM using the BAPI - BAPI_MATERIAL_BOM_GROUP_CREATE. My requirement is to create BOM components with Valid From and Valid TO dates. This BAPI has Valid From Date field whereas no field available to enter Valid-To Date. The BAPI gets created with components but the Valid To date is defaulted to 12/31/9999. I dont want this. I have my own Valid TO dates in the file and I want those to appear. How to go about it?
Thanks
Shakir.
Edited by: Shakir on Jul 30, 2008 11:36 AM

hi,
i too faced the problem ...then i went for bdc.....here is the code
*& Report ZPP_REPORT_BOM
*& Created By : shailaja
*& Created on : 09.02.2007
*& Requested By :
*& Description : Master Data Upload BOM
REPORT ZPP_REPORT_BOM NO STANDARD PAGE HEADING LINE-SIZE 255.
Structure Declaration
TYPES : BEGIN OF TY_SOURCE,
MATNR(18),
WERKS(4),
STLAN(1),
STLAL(2),
DATUV(10),
POSNR(4), " BOM item number
POSTP(1), " BOM Item category
IDNRK(18),
MENGE(13),
MEINS(3),
AVOAU(3), " Operation Scrap
NETAU, " Indicator: Net scrap
ALPGR(2),
ALPRF(2),
ALPST(1),
EWAHR(3),
LGORT(4), " Storage Location
BMENG(13),
STLST(2),
END OF TY_SOURCE,
BEGIN OF TY_HEADER ,
MATNR(18),
WERKS(4),
STLAN(1),
STLAL(2),
DATUV(10),
BMENG(13),
LOSVN(2),
LOSBS(2),
STLST(2),
END OF TY_HEADER,
BEGIN OF TY_ITEM ,
MATNR(18),
POSNR(4),
POSTP(1),
IDNRK(18),
MENGE(13),
MEINS(3),
AUSCH(5),
AVOAU(3),
NETAU,
ALPGR(2),
ALPRF(2),
ALPST(1),
EWAHR(3),
LGORT(4),
END OF TY_ITEM.
Internal Table Declaration
DATA : T_SOURCE TYPE STANDARD TABLE OF TY_SOURCE INITIAL SIZE 1,
T_HEADER TYPE STANDARD TABLE OF TY_HEADER INITIAL SIZE 1,
T_ITEM TYPE STANDARD TABLE OF TY_ITEM INITIAL SIZE 1,
T_TARGET TYPE STANDARD TABLE OF BDCDATA INITIAL SIZE 1.
DATA : W_SOURCE TYPE TY_SOURCE,
W_SOURCE1 TYPE TY_SOURCE,
W_HEADER TYPE TY_HEADER,
W_ITEM TYPE TY_ITEM,
W_TARGET TYPE BDCDATA,
COUNT TYPE I.
Variable Declaration
DATA: W_FNAME TYPE STRING,
FNAM(20),
I(2) TYPE N,
V_COUNT TYPE I,
V_GROUP TYPE APQI-GROUPID.
SELECTION SCREEN CRITERIA
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETERS : P_PATH TYPE RLGRAP-FILENAME,
P_GROUP(15) DEFAULT 'BOM'.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_PATH.
CALL FUNCTION 'WS_FILENAME_GET'
EXPORTING
DEF_FILENAME = 'C:\TEST.TXT'
DEF_PATH = 'C:\Documents and Settings\Naidu\Desktop\TEST-1.txt'
MASK = ',.,..'
MODE = 'O' "O --> Open S --> Save
TITLE = 'OPEN'
IMPORTING
FILENAME = P_PATH
RC =
EXCEPTIONS
INV_WINSYS = 1
NO_BATCH = 2
SELECTION_CANCEL = 3
SELECTION_ERROR = 4
OTHERS = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
START-OF-SELECTION
START-OF-SELECTION.
PERFORM SUB_UPLOAD.
PERFORM SUB_BDC_PROCESS.
PERFORM SUB_CLOSE.
WRITE:/ 'The session', V_GROUP ,'has been successfully created with',
V_COUNT.
WRITE:/ 'Please process the session in SM35'.
*& PERFORM SUB_UPLOAD
FORM SUB_UPLOAD.
W_FNAME = P_PATH.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = W_FNAME
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
DATA_TAB = T_SOURCE
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT T_SOURCE INTO W_SOURCE.
W_SOURCE1 = W_SOURCE.
AT NEW MATNR.
W_HEADER-MATNR = W_SOURCE1-MATNR.
W_HEADER-WERKS = W_SOURCE1-WERKS.
W_HEADER-STLAN = W_SOURCE1-STLAN.
W_HEADER-DATUV = W_SOURCE1-DATUV.
W_HEADER-BMENG = W_SOURCE1-BMENG.
W_HEADER-STLAL = W_SOURCE1-STLAL.
W_HEADER-STLST = W_SOURCE1-STLST.
APPEND W_HEADER TO T_HEADER.
ENDAT.
W_ITEM-MATNR = W_SOURCE1-MATNR.
W_ITEM-IDNRK = W_SOURCE1-IDNRK.
W_ITEM-MENGE = W_SOURCE1-MENGE.
W_ITEM-MEINS = W_SOURCE1-MEINS.
W_ITEM-POSTP = W_SOURCE1-POSTP.
W_ITEM-POSNR = W_SOURCE1-POSNR.
W_ITEM-AVOAU = W_SOURCE1-AVOAU.
W_ITEM-LGORT = W_SOURCE1-LGORT.
W_ITEM-NETAU = W_SOURCE1-NETAU.
W_ITEM-ALPGR = W_SOURCE1-ALPGR.
W_ITEM-ALPRF = W_SOURCE1-ALPRF.
W_ITEM-ALPST = W_SOURCE1-ALPST.
W_ITEM-EWAHR = W_SOURCE1-EWAHR.
APPEND W_ITEM TO T_ITEM.
CLEAR :W_ITEM,W_HEADER.
ENDLOOP.
ENDFORM. "Sub_upload
*& PERFORM SUB_BDC_PROCESS
FORM SUB_BDC_PROCESS.
V_GROUP = P_GROUP.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
DEST = FILLER8
GROUP = V_GROUP "'BOM'
HOLDDATE = FILLER8
KEEP = 'X'
USER = SY-UNAME
RECORD = FILLER1
PROG = SY-CPROG
IMPORTING
QID =
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT T_HEADER INTO W_HEADER.
REFRESH T_TARGET.
perform bdc_dynpro using 'SAPLCSDI' '0100'.
perform bdc_field using 'BDC_CURSOR' 'RC29N-DATUV'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'RC29N-MATNR' W_HEADER-MATNR."'FZGN25051641'.
perform bdc_field using 'RC29N-WERKS' W_HEADER-WERKS."'2200'.
perform bdc_field using 'RC29N-STLAN' W_HEADER-STLAN."'1'.
PERFORM BDC_FIELD USING 'RC29N-STLAL' W_HEADER-STLAL.
perform bdc_field using 'RC29N-DATUV' W_HEADER-DATUV."'31122005'.
perform bdc_dynpro using 'SAPLCSDI' '0110'.
perform bdc_field using 'BDC_CURSOR' 'RC29K-BMENG'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'RC29K-BMENG' W_HEADER-BMENG."'1668'.
PERFORM BDC_FIELD USING 'RC29K-STLST' W_HEADER-STLST."'1'.
perform bdc_dynpro using 'SAPLCSDI' '0111'.
perform bdc_field using 'BDC_CURSOR' 'RC29K-LABOR'.
perform bdc_field using 'BDC_OKCODE' '/00'.
I = 1.
LOOP AT T_ITEM INTO W_ITEM WHERE MATNR = W_HEADER-MATNR.
COUNT = COUNT + 1.
IF COUNT GT 14.
CLEAR I.
I = 2.
BREAK KISHORES.
perform bdc_dynpro using 'SAPLCSDI' '0140'.
perform bdc_field using 'BDC_OKCODE' '=FCNP'.
ENDIF.
perform bdc_dynpro using 'SAPLCSDI' '0140'.
perform bdc_field using 'BDC_CURSOR' 'RC29P-SORTF(01)'.
perform bdc_field using 'BDC_OKCODE' '/00'.
CONCATENATE 'RC29P-IDNRK(' I ')' INTO FNAM.
perform bdc_field using FNAM W_ITEM-IDNRK.
CONCATENATE 'RC29P-MENGE(' I ')' INTO FNAM.
perform bdc_field using FNAM W_ITEM-MENGE.
CONCATENATE 'RC29P-MEINS(' I ')' INTO FNAM.
perform bdc_field using FNAM W_ITEM-MEINS.
CONCATENATE 'RC29P-POSTP(' I ')' INTO FNAM.
perform bdc_field using FNAM W_ITEM-POSTP.
CONCATENATE 'RC29P-POSNR(' I ')' INTO FNAM.
PERFORM BDC_FIELD USING FNAM W_ITEM-POSNR.
perform bdc_dynpro using 'SAPLCSDI' '0130'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'BDC_CURSOR' 'RC29P-ALPGR'.
PERFORM BDC_FIELD USING 'RC29P-NETAU' W_ITEM-NETAU.
PERFORM BDC_FIELD USING 'RC29P-AVOAU' W_ITEM-AVOAU.
perform bdc_field using 'RC29P-ALPGR' W_ITEM-ALPGR.
IF W_ITEM-ALPGR = ' '.
ELSE.
perform bdc_dynpro using 'SAPLCSDI' '0716'.
perform bdc_field using 'BDC_CURSOR' 'RC29P-EWAHR'.
perform bdc_field using 'BDC_OKCODE' '=CLWI'.
perform bdc_field using 'RC29P-ALPRF' W_ITEM-ALPRF.
perform bdc_field using 'RC29P-ALPST' W_ITEM-ALPST.
perform bdc_field using 'RC29P-EWAHR' W_ITEM-EWAHR.
ENDIF.
perform bdc_dynpro using 'SAPLCSDI' '0131'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'BDC_CURSOR' 'RC29P-POTX1'.
perform bdc_field using 'RC29P-SANKA' 'X'.
PERFORM BDC_FIELD USING 'RC29P-LGORT' W_ITEM-LGORT.
I = I + 1.
CLEAR W_ITEM.
ENDLOOP.
perform bdc_dynpro using 'SAPLCSDI' '0140'.
perform bdc_field using 'BDC_CURSOR' 'RC29P-POSNR(01)'.
perform bdc_field using 'BDC_OKCODE' '=FCBU'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = 'CS01'
POST_LOCAL = NOVBLOCAL
PRINTING = NOPRINT
SIMUBATCH = ' '
CTUPARAMS = ' '
TABLES
DYNPROTAB = T_TARGET
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
V_COUNT = V_COUNT + 1.
ENDIF.
CLEAR : W_ITEM,W_HEADER.
ENDLOOP.
ENDFORM. "SUB_BDC_PROCESS
*& Form SUB_CLOSE
text
--> p1 text
<-- p2 text
FORM SUB_CLOSE .
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " SUB_CLOSE
Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR W_TARGET.
W_TARGET-PROGRAM = PROGRAM.
W_TARGET-DYNPRO = DYNPRO.
W_TARGET-DYNBEGIN = 'X'.
APPEND W_TARGET TO T_TARGET.
ENDFORM. "BDC_DYNPRO
Insert field *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
CLEAR W_TARGET.
W_TARGET-FNAM = FNAM.
W_TARGET-FVAL = FVAL.
APPEND W_TARGET TO T_TARGET.
ENDIF.
ENDFORM. "BDC_FIELD

Please add XSD Schema for validating TLF data in TLF 3.0

It would be very beneficial to have a XSD schema for validating TLF data. Please add this to TLF 3.0. There are a couple of posts where others have already asked for this...
http://forums.adobe.com/message/2795099#2795099
http://forums.adobe.com/message/2223205
Thanks!

Sure Gang!
We could use the XML schema to validate the TLF markup that we are generating from our publishing system. We generate XML files which include the TLF markup and a XML schema would be very beneficial to validate that markup to make sure we are doing everything right.

Bex Error : period 0000000 - No Valid translation date to specify (Z_FRCPE)

Hi Experts,
While executing the reports with few selection we are getting the below warning message :
period 0000000 - No Valid translation date to specify (Z_FRCPE)
period 0000000 - No Valid translation date to specify (ZMOEND )
I want to know why this warning message is comming up.what is the reason for the same.
Kindly advise.
Thanks & regards,
M.S

Hi Experts,
I found the SAP Note 671810 - Period 0000000 - hiding BRAIN 385.This notes speaks to import the package SAPKW30B17 and we are already in the ahead version.
So I would like to know that why this particular warning message pops up in the report after execution.we are unware regarding the same.
Thanks & regards,
M.S

Validating audio data message

Similar Messages

Maybe you are looking for